From: Laurent Riffard <laurent.riffard@free.fr>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: BUG on reiser4_delete_inode
Date: Fri, 05 May 2006 18:55:11 +0200 [thread overview]
Message-ID: <445B836F.2000702@free.fr> (raw)
In-Reply-To: <1146836304.6254.26.camel@tribesman.namesys.com>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
Le 05.05.2006 15:38, Vladimir V. Saveliev a écrit :
> Hello
>
> On Thu, 2006-05-04 at 22:21 +0200, Laurent Riffard wrote:
>> Hello,
>>
>> I have a small Reiser4 FS (1 GB) which became really unstable since
>> 2.6.17-rc2-mm1. I managed to get a fully reproductible scenario:
>>
>> sh-3.00# mount /dev/vglinux1/lvkernel2 /mnt/disk
>>
>> ~$ mv /mnt/disk/linux-2.6-stable/arch/i386/kernel/acpi/boot.c /home/laurent/tmp/
>> Erreur de segmentation
>>
>> ------------[ cut here ]------------
>> kernel BUG at fs/inode.c:251!
>
> Thanks for the report. The problem is introduced by
> ftp://ftp.ru.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc2/2.6.17-rc2-mm1/broken-out/radix-tree-direct-data.patch
>
> The attached patch should fix the problem, though.
Ok, this bug seems to be fixed.
Thanks for your quick answer.
--
laurent
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2006-05-05 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 20:21 BUG on reiser4_delete_inode Laurent Riffard
[not found] ` <1146836304.6254.26.camel@tribesman.namesys.com>
2006-05-05 16:55 ` Laurent Riffard [this message]
2006-05-05 18:32 ` Joe Feise
2006-05-06 5:51 ` Laurent Riffard
2006-05-06 6:27 ` Joe Feise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=445B836F.2000702@free.fr \
--to=laurent.riffard@free.fr \
--cc=reiserfs-list@namesys.com \
--cc=vs@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.