summaryrefslogtreecommitdiffstats
path: root/fs/stat.c
diff options
context:
space:
mode:
authorYongqiang Yang <xiaoqiangnk@gmail.com>2011-12-28 23:46:46 +0100
committerTheodore Ts'o <tytso@mit.edu>2011-12-28 23:46:46 +0100
commit1ba37268cd19e5a2a80924bfe8618bf1ba3e8249 (patch)
treef4227aaf3963e6c948b01e57c98697e6ab2157d6 /fs/stat.c
parentext4: flush journal when switching from data=journal mode (diff)
downloadlinux-1ba37268cd19e5a2a80924bfe8618bf1ba3e8249.tar.xz
linux-1ba37268cd19e5a2a80924bfe8618bf1ba3e8249.zip
jbd2: clear revoked flag on buffers before a new transaction started
Currently, we clear revoked flag only when a block is reused. However, this can tigger a false journal error. Consider a situation when a block is used as a meta block and is deleted(revoked) in ordered mode, then the block is allocated as a data block to a file. At this moment, user changes the file's journal mode from ordered to journaled and truncates the file. The block will be considered re-revoked by journal because it has revoked flag still pending from the last transaction and an assertion triggers. We fix the problem by keeping the revoked status more uptodate - we clear revoked flag when switching revoke tables to reflect there is no revoked buffers in current transaction any more. Signed-off-by: Yongqiang Yang <xiaoqiangnk@gmail.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs/stat.c')
0 files changed, 0 insertions, 0 deletions