public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at buffer.c:827 in test12-pre6 and 7
Date: 7 Dec 2000 16:22:39 -0800	[thread overview]
Message-ID: <90p9kf$5p3$1@penguin.transmeta.com> (raw)
In-Reply-To: <3A30125D.5F71110D@cheek.com>

In article <3A30125D.5F71110D@cheek.com>,
Joseph Cheek  <joseph@cheek.com> wrote:
>copying files off a loopback-mounted vfat filesystem exposes this bug.
>test11 worked fine.

It's not a new bug - it's an old bug that apparently is uncovered by a
new stricter test.

Apparently loopback unlocks an already unlocked page - which has always
been a serious offense, but has never been detected before.

test12-pre6+ detects it, and thus the BUG().

Your stack trace isn't symbolic (see Documentation/oops-tracing.txt), so
it's impossible to debug, but it's already interesting information to
see that it seems to be either loopback of vfat.

Can you test some more? In particular, I'd love to hear if this happens
with vfat even without loopback, or with loopback even without vfat
(make an ext2 filesystem or similar instead). That woul dnarrow down the
bug further.

		Thanks,
				Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-12-08  0:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-07 22:42 kernel BUG at buffer.c:827 in test12-pre6 and 7 Joseph Cheek
2000-12-07 23:14 ` Keith Owens
2000-12-08  0:22 ` Linus Torvalds [this message]
2000-12-08  1:23   ` Joseph Cheek
2000-12-08  3:03     ` Keith Owens
2000-12-08  2:16   ` Joseph Cheek
2000-12-08  7:27   ` Tom Leete
2000-12-08  9:07 ` David Woodhouse
2000-12-08  9:58   ` [found?] " Alexander Viro
2000-12-08 18:11     ` [PATCH] " Alexander Viro
2000-12-08 18:48       ` Linus Torvalds
2000-12-08 19:13         ` Alexander Viro
2000-12-08 19:39           ` Linus Torvalds
2000-12-08 19:50             ` Daniel Phillips
2000-12-08 21:17               ` Linus Torvalds
2000-12-08 22:30             ` Alexander Viro
2000-12-08 22:42               ` Linus Torvalds
2000-12-09  4:59                 ` Alexander Viro
2000-12-09  8:45                   ` Linus Torvalds
2000-12-09  8:56                     ` Linus Torvalds
2000-12-09 10:40                     ` Alexander Viro
2000-12-09 12:56                       ` Andries Brouwer
2000-12-09 13:11                         ` Alexander Viro
2000-12-09 21:25                           ` Mikulas Patocka
2000-12-10  1:11                             ` Linus Torvalds
2000-12-09 17:28                       ` Linus Torvalds
2000-12-09 18:43                         ` Andi Kleen
2000-12-09 14:00                     ` David S. Miller
2000-12-09 15:37           ` David Woodhouse
2000-12-12  0:54 ` [FIXED!] " Joseph Cheek

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='90p9kf$5p3$1@penguin.transmeta.com' \
    --to=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox