diff options
author | Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> | 2011-02-28 13:41:11 +0900 |
---|---|---|
committer | Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> | 2011-03-02 09:55:18 +0900 |
commit | 72746ac643928f6c3113b5aa783d8ea1b13949d2 (patch) | |
tree | c1d151eae5e963dd3f57079e0287c2259257bc29 /Documentation/CodingStyle | |
parent | dd9c1549edef02290edced639f67b54a25abbe0e (diff) | |
download | blackbird-op-linux-72746ac643928f6c3113b5aa783d8ea1b13949d2.tar.gz blackbird-op-linux-72746ac643928f6c3113b5aa783d8ea1b13949d2.zip |
nilfs2: fix regression that i-flag is not set on changeless checkpoints
According to the report from Jiro SEKIBA titled "regression in
2.6.37?" (Message-Id: <8739n8vs1f.wl%jir@sekiba.com>), on 2.6.37 and
later kernels, lscp command no longer displays "i" flag on checkpoints
that snapshot operations or garbage collection created.
This is a regression of nilfs2 checkpointing function, and it's
critical since it broke behavior of a part of nilfs2 applications.
For instance, snapshot manager of TimeBrowse gets to create
meaningless snapshots continuously; snapshot creation triggers another
checkpoint, but applications cannot distinguish whether the new
checkpoint contains meaningful changes or not without the i-flag.
This patch fixes the regression and brings that application behavior
back to normal.
Reported-by: Jiro SEKIBA <jir@unicus.jp>
Signed-off-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Tested-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Tested-by: Jiro SEKIBA <jir@unicus.jp>
Cc: stable <stable@kernel.org> [2.6.37]
Diffstat (limited to 'Documentation/CodingStyle')
0 files changed, 0 insertions, 0 deletions