From: Hans Reiser <reiser@namesys.com>
To: Oleg Drokin <green@namesys.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.67 - reiserfs go boom.
Date: Wed, 09 Apr 2003 11:24:56 +0400 [thread overview]
Message-ID: <3E93CAC8.8070407@namesys.com> (raw)
In-Reply-To: <20030409105339.A26788@namesys.com>
Oleg Drokin wrote:
>Hello!
>
>On Wed, Apr 09, 2003 at 02:18:02AM +0100, Dave Jones wrote:
>
>
>
>>Whilst running fsx.. (Though fsx didn't trigger any error,
>>and is still running)..
>>buffer layer error at fs/buffer.c:127
>>Call Trace:
>> [<c016d260>] __wait_on_buffer+0xd0/0xe0
>> [<c0121760>] autoremove_wake_function+0x0/0x50
>> [<c0121760>] autoremove_wake_function+0x0/0x50
>> [<c02886c8>] reiserfs_unmap_buffer+0x68/0xa0
>>
>>
>
>Andrew Morton said "That's not a bug. It is errant debugging code." because the page is locked by us,
>so buffers are safe.
>So I am not looking into this and hoping that somebody will fix the debugging code instead ;)
>
>Bye,
> Oleg
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
Oleg, if someone doesn't do it for you in 7 days, you must do it....
errant debugging code is a bug.... when users (reasonably) think our fs
has bugs, that needs to be fixed;-)
--
Hans
prev parent reply other threads:[~2003-04-09 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 1:18 2.5.67 - reiserfs go boom Dave Jones
2003-04-09 1:56 ` Steven Cole
2003-04-09 15:48 ` Dave Kleikamp
2003-04-09 6:53 ` Oleg Drokin
2003-04-09 7:24 ` Hans Reiser [this message]
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=3E93CAC8.8070407@namesys.com \
--to=reiser@namesys.com \
--cc=davej@codemonkey.org.uk \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
/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.