From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alexander Viro <viro@math.psu.edu>,
Linus Torvalds <torvalds@transmeta.com>,
Paul Mackerras <paulus@linuxcare.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: page->mapping == 0
Date: Sun, 29 Oct 2000 15:26:48 -0700 [thread overview]
Message-ID: <39FCA428.F89746F3@timpanogas.org> (raw)
In-Reply-To: <E13pz7a-0006JY-00@the-village.bc.nu>
Alan Cox wrote:
>
> > I would expect problems with truncate, mmap, rename, POSIX locks, fasync,
> > ptrace and mount go unnoticed for _long_. Ditto for parts of procfs
>
> Well the ptrace one still has mysteriously breaks usermode linux against it
> on my list here. Was that ever explained. It looked like the stack got corrupted
> which is weird.
Do any of you guys have an SMP inverse assembler handy? This bug is
scary as shit, and someone needs to setup an SMP ICE and actually trace
through the code (and set address breakpoints) to see just what is going
on. It really is sounding like a race condition of some kind, and I
read everyone's "speculation" about what they think is happneing, but
how about getting some hardware tools, and tracking is down. It feels
like an MMU bug of some type. Who has access to Yellow Cover Intel
Errata sheets? It may be a hardware bug intel knows about but we don't
-- their MMU is so bug infested how do we know it's not one of these.
I don't think you guys have a good handle on it yet. Linus seems to
think it's a coding problem with a race somewhere. How about someone
getting some hardware tools and nailing the puppy to the floor so 2.4
can get out the door...
:-)
Jeff
>
> -
> 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/
-
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/
next prev parent reply other threads:[~2000-10-29 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14841.7644.853174.666385@argo.linuxcare.com.au>
[not found] ` <Pine.LNX.4.10.10010262325440.864-100000@penguin.transmeta.com>
2000-10-29 9:38 ` page->mapping == 0 Paul Mackerras
2000-10-29 12:39 ` Daniel Phillips
2000-10-29 18:05 ` Linus Torvalds
2000-10-29 18:32 ` Alexander Viro
2000-10-29 19:12 ` Linus Torvalds
2000-10-29 19:33 ` Linus Torvalds
2000-10-30 1:57 ` Daniel Phillips
2000-10-29 20:32 ` Alan Cox
2000-10-29 20:42 ` Alexander Viro
2000-10-29 22:26 ` Jeff V. Merkey [this message]
2000-10-29 23:12 ` Jeff Dike
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=39FCA428.F89746F3@timpanogas.org \
--to=jmerkey@timpanogas.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@linuxcare.com.au \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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