diff options
author | Jan Kara <jack@suse.cz> | 2010-08-05 12:38:26 +0200 |
---|---|---|
committer | Jan Kara <jack@suse.cz> | 2010-08-05 21:28:28 +0200 |
commit | 5f11e6a44059f728dddd8d0dbe5b4368ea93575b (patch) | |
tree | c66eed7a13b1de48d9a6539b9a7c7a27bda706c6 /fs/gfs2 | |
parent | aa32a796389bedbcf1c7714385b18714a0743810 (diff) | |
download | op-kernel-dev-5f11e6a44059f728dddd8d0dbe5b4368ea93575b.zip op-kernel-dev-5f11e6a44059f728dddd8d0dbe5b4368ea93575b.tar.gz |
ext3: Fix dirtying of journalled buffers in data=journal mode
In data=journal mode, we still use block_write_begin() to prepare page for
writing. This function can occasionally mark buffer dirty which violates
journalling assumptions - when a buffer is part of a transaction, it should be
dirty and a buffer can be already part of a forget list of some transaction
when block_write_begin() gets called. This violation of journalling assumptions
then results in "JBD: Spotted dirty metadata buffer..." warnings.
In fact, temporary dirtying the buffer while the page is still locked does not
really cause problems to the journalling because we won't write the buffer
until the page gets unlocked. So we just have to make sure to clear dirty bits
before unlocking the page.
Reviewed-by: "Theodore Ts'o" <tytso@mit.edu>
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'fs/gfs2')
0 files changed, 0 insertions, 0 deletions