aboutsummaryrefslogtreecommitdiffstats
path: root/fs/nilfs2/gcinode.c
diff options
context:
space:
mode:
authorRyusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>2010-07-07 17:19:54 +0900
committerRyusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>2010-07-23 10:02:12 +0900
commitcfa913a5077f7619869b2b4d1bf23ccb4f8b3d7b (patch)
treef4d8e4e8d8ee220b448566a08e75bccfb0ca966f /fs/nilfs2/gcinode.c
parent7c01745781177795e39f78b2c2c42c470a13833a (diff)
downloadkernel_samsung_smdk4412-cfa913a5077f7619869b2b4d1bf23ccb4f8b3d7b.zip
kernel_samsung_smdk4412-cfa913a5077f7619869b2b4d1bf23ccb4f8b3d7b.tar.gz
kernel_samsung_smdk4412-cfa913a5077f7619869b2b4d1bf23ccb4f8b3d7b.tar.bz2
nilfs2: add sanity check in nilfs_btree_add_dirty_buffer
According to the report titled "problem with nilfs_cleanerd" from Łukasz Wójcicki, nilfs_btree_lookup_dirty_buffers or nilfs_btree_add_dirty_buffer got memory violation during garbage collection. This could happen if a level field of given btree node buffer is incorrect, which is a crucial internal bug. This inserts a sanity check to figure out the problem. Signed-off-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Diffstat (limited to 'fs/nilfs2/gcinode.c')
0 files changed, 0 insertions, 0 deletions