hello
On Sat, 2006-05-13 at 22:03 +0200, Laurent Riffard wrote:
> Hello,
>
> I've been hit by a couple of reiser4 panic due to zam-397 assertion.
> It's more or less reproducible. How can I help debug this ?
This looks like known bug in debugging code.
Please try to reproduce the problem with the attached patch.
> ~~
> laurent
>
fs/reiser4/plugin/space/bitmap.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -puN fs/reiser4/plugin/space/bitmap.c~reiser4-fix-block-alloc-assertions fs/reiser4/plugin/space/bitmap.c
--- linux-2.6.17-rc3-mm1/fs/reiser4/plugin/space/bitmap.c~reiser4-fix-block-alloc-assertions 2006-05-15 13:45:57.000000000 +0400
+++ linux-2.6.17-rc3-mm1-vs/fs/reiser4/plugin/space/bitmap.c 2006-05-15 13:51:30.000000000 +0400
@@ -1113,7 +1113,7 @@ alloc_blocks_forward(reiser4_blocknr_hin
assert("zam-398", super != NULL);
assert("zam-412", hint != NULL);
- assert("zam-397", hint->blk < reiser4_block_count(super));
+ assert("zam-397", hint->blk <= reiser4_block_count(super));
if (hint->max_dist == 0)
search_end = reiser4_block_count(super);
@@ -1160,7 +1160,7 @@ static int alloc_blocks_backward(reiser4
assert("zam-969", super != NULL);
assert("zam-970", hint != NULL);
- assert("zam-971", hint->blk < reiser4_block_count(super));
+ assert("zam-971", hint->blk <= reiser4_block_count(super));
search_start = hint->blk;
if (hint->max_dist == 0 || search_start <= hint->max_dist)
_
