From: Theodore Ts'o <tytso@mit.edu>
Date: Wed, 16 Mar 2011 21:16:31 +0000 (-0400)
Subject: ext4: Initialize fsync transaction ids in ext4_new_inode()
X-Git-Tag: v2.6.39-rc1~73^2~12
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=688f869ce3bdc892daa993534dc6df18c95df931;p=pandora-kernel.git

ext4: Initialize fsync transaction ids in ext4_new_inode()

When allocating a new inode, we need to make sure i_sync_tid and
i_datasync_tid are initialized.  Otherwise, one or both of these two
values could be left initialized to zero, which could potentially
result in BUG_ON in jbd2_journal_commit_transaction.

(This could happen by having journal->commit_request getting set to
zero, which could wake up the kjournald process even though there is
no running transaction, which then causes a BUG_ON via the
J_ASSERT(j_ruinning_transaction != NULL) statement.

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
---

Reading git-diff-tree failed