ext4: Initialize fsync transaction ids in ext4_new_inode()
authorTheodore Ts'o <tytso@mit.edu>
Wed, 16 Mar 2011 21:16:31 +0000 (17:16 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Wed, 16 Mar 2011 21:16:31 +0000 (17:16 -0400)
commit688f869ce3bdc892daa993534dc6df18c95df931
treeaea78b966a70e3e0200a88bfaddb86e7fd3f1092
parent198868f35de99e7197829314076e5465c37e4cc5
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>
fs/ext4/ialloc.c
This page took 0.032125 seconds and 5 git commands to generate.