From: "Stephen C. Tweedie" <sct@redhat.com>
To: Jeff Schaller <schaller@freeshell.org>
Cc: sct@redhat.com, akpm@zip.com.au, adilger@clusterfs.com,
mingo@redhat.com, neilb@cse.unsw.edu.au, ext3-users@redhat.com,
linux-raid@vger.kernel.org
Subject: Re: Assertion failure, BUG at journal.c:1732
Date: Mon, 25 Nov 2002 15:08:25 +0000 [thread overview]
Message-ID: <20021125150825.A11869@redhat.com> (raw)
In-Reply-To: <Pine.NEB.4.44.0211232017520.8377-200000@iceland.freeshell.org>; from schaller@freeshell.org on Sat, Nov 23, 2002 at 08:18:26PM +0000
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
Hi,
On Sat, Nov 23, 2002 at 08:18:26PM +0000, Jeff Schaller wrote:
> Boy, it'd help if I actually attached the log, eh?
Yes. :)
Content-Description: kern.log
> Nov 19 06:58:47 debian kernel: attempt to access beyond end of device
> Nov 19 06:58:47 debian kernel: 09:00: rw=1, want=39121480, limit=39121408
Corruption on disk. Undiagnosable without more info --- it could be
hardware or software.
> Nov 19 06:58:47 debian kernel: Assertion failure in __journal_remove_journal_head() at journal.c:1732: "buffer_jbd(bh)"
> Nov 19 06:58:47 debian kernel: kernel BUG at journal.c:1732!
That's a core driver layer bug which we found recently, but it's
too close to 2.4.20 to include the fix. Basically, on an
out-of-bounds IO the ll_rw_block code was clearing most of the bits in
the buffer_head state, leading to the above assert failure when ext3
found its critical metadata had been corrupted.
Patch is below, I'll send it to Marcelo for 2.4.21-pre.
--Stephen
[-- Attachment #2: 000-buffer_clearbits.patch --]
[-- Type: text/plain, Size: 632 bytes --]
--- linux-2.4-ext3merge/drivers/block/ll_rw_blk.c.=K0026=.orig Mon Nov 25 15:03:18 2002
+++ linux-2.4-ext3merge/drivers/block/ll_rw_blk.c Mon Nov 25 15:04:00 2002
@@ -1129,7 +1129,7 @@
if (maxsector < count || maxsector - count < sector) {
/* Yecch */
- bh->b_state &= (1 << BH_Lock) | (1 << BH_Mapped);
+ bh->b_state &= ~(1 << BH_Dirty);
/* This may well happen - the kernel calls bread()
without checking the size of the device, e.g.,
@@ -1140,7 +1140,6 @@
kdevname(bh->b_rdev), rw,
(sector + count)>>1, minorsize);
- /* Yecch again */
bh->b_end_io(bh, 0);
return;
}
prev parent reply other threads:[~2002-11-25 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 19:43 Assertion failure, BUG at journal.c:1732 Jeff Schaller
2002-11-23 20:18 ` Jeff Schaller
2002-11-24 23:42 ` Theodore Ts'o
2002-12-02 11:15 ` Jeff Schaller
2002-11-25 15:08 ` Stephen C. Tweedie [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=20021125150825.A11869@redhat.com \
--to=sct@redhat.com \
--cc=adilger@clusterfs.com \
--cc=akpm@zip.com.au \
--cc=ext3-users@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@cse.unsw.edu.au \
--cc=schaller@freeshell.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.