From: Andrew Morton <akpm@zip.com.au>
To: Ryan Mack <rmack@mackman.net>
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [BUG] 2.4.10/0.9.10 "VFS: brelse: Trying to free free buffer"
Date: Tue, 02 Oct 2001 10:02:08 -0700 [thread overview]
Message-ID: <3BB9F310.C7CB057@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0110020213100.9833-300000@mackman.net>
Ryan Mack wrote:
>
> Unfortunately I don't have an oops or a stack trace to report where this
> message came from, but at least maybe this report can alert someone who
> can spot the bug in the code. This occurred under light usage on an ext3
> partition built on a 2 disk RAID-1 mirrored array.
>
> The array was either two IDE disks using data-ordered mode or two SCSI
> disks using data-journal mode.
>
Yes, that shouldn't be happening. If it is reproducible, could
you please add
print_buffer_trace(buf);
to the very end of fs/buffer.c:__brelse() and recompile with
CONFIG_BUFFER_TRACE=y?
Thanks.
prev parent reply other threads:[~2001-10-02 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 9:23 [BUG] 2.4.10/0.9.10 "VFS: brelse: Trying to free free buffer" Ryan Mack
2001-10-02 17:02 ` Andrew Morton [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=3BB9F310.C7CB057@zip.com.au \
--to=akpm@zip.com.au \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmack@mackman.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox