summaryrefslogtreecommitdiffstats
path: root/fs/debugfs/file.c
diff options
context:
space:
mode:
authorRyusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>2011-02-28 05:41:11 +0100
committerRyusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>2011-03-02 01:55:18 +0100
commit72746ac643928f6c3113b5aa783d8ea1b13949d2 (patch)
treec1d151eae5e963dd3f57079e0287c2259257bc29 /fs/debugfs/file.c
parentLinux 2.6.38-rc7 (diff)
downloadlinux-72746ac643928f6c3113b5aa783d8ea1b13949d2.tar.xz
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 'fs/debugfs/file.c')
0 files changed, 0 insertions, 0 deletions