summaryrefslogtreecommitdiffstats
path: root/lib/parser.c
diff options
context:
space:
mode:
authorRyusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>2010-03-22 13:36:06 +0100
committerRyusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>2010-03-23 16:03:06 +0100
commit110d735a0ae69bdd11af9acb6ea3b979137eb118 (patch)
treeaa25160aad878031823920a00e802ac3da76b5bb /lib/parser.c
parentnilfs2: fix duplicate call to nilfs_segctor_cancel_freev (diff)
downloadlinux-110d735a0ae69bdd11af9acb6ea3b979137eb118.tar.xz
linux-110d735a0ae69bdd11af9acb6ea3b979137eb118.zip
nilfs2: fix hang-up of cleaner after log writer returned with error
According to the report from Andreas Beckmann (Message-ID: <4BA54677.3090902@abeckmann.de>), nilfs in 2.6.33 kernel got stuck after a disk full error. This turned out to be a regression by log writer updates merged at kernel 2.6.33. nilfs_segctor_abort_construction, which is a cleanup function for erroneous cases, was skipping writeback completion for some logs. This fixes the bug and would resolve the hang issue. Reported-by: Andreas Beckmann <debian@abeckmann.de> Signed-off-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> Tested-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> Cc: stable <stable@kernel.org> [2.6.33.x]
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions