From: Andrea Arcangeli <andrea@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Jeff Dike <jdike@karaya.com>,
user-mode-linux-user@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: user-mode port 0.44-2.4.7
Date: Mon, 23 Jul 2001 19:50:55 +0200 [thread overview]
Message-ID: <20010723195055.A16919@athlon.random> (raw)
In-Reply-To: <20010723184528.R822@athlon.random> <Pine.LNX.4.33.0107231031380.13231-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0107231031380.13231-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Mon, Jul 23, 2001 at 10:32:32AM -0700
On Mon, Jul 23, 2001 at 10:32:32AM -0700, Linus Torvalds wrote:
>
> On Mon, 23 Jul 2001, Andrea Arcangeli wrote:
> >
> > it's the other way around, it's needed and gcc trapped a kernel bug.
>
> No it's not.
>
> > If the contents of memory not declared volatile changes under GCC (like
> > it can happen right now for xtime since it's declared non volatile), gcc
> > has the full rights to crash the kernel at runtime.
>
> Absolutely not.
>
> If we care abotu the thing always having the same value, we HAVE to use a
> lock. "volatile" is not the answer.
>
> Show me a place where we care.
The problem is not at the source code level, of course all places where
we read the xtime cannot crash the kernel as far as the kernel is
concerned, but the problem is instead at the gcc level: and when the
logic implemented by the asm generated by gcc chokes we can also get a
dangling poitner and crash in the kernel.
GCC internally is allowed to generate code that relies on the contents
of the memory to stay constant, this because of the C standard, the
usual example is a fast path jump table for the "case" statement.
So in short having non volatile memory that changes under gcc gives gcc
the full rights to crash the kernel at runtime anytime.
Andrea
next prev parent reply other threads:[~2001-07-23 17:50 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 5:08 user-mode port 0.44-2.4.7 Jeff Dike
2001-07-23 15:56 ` Andrea Arcangeli
2001-07-23 15:59 ` Andrea Arcangeli
2001-07-23 16:17 ` Andrea Arcangeli
2001-07-23 16:51 ` Andrea Arcangeli
2001-07-23 16:33 ` Linus Torvalds
2001-07-23 16:45 ` Andrea Arcangeli
2001-07-23 17:32 ` Linus Torvalds
2001-07-23 17:50 ` Andrea Arcangeli [this message]
2001-07-23 18:11 ` Linus Torvalds
2001-07-23 18:27 ` Andrea Arcangeli
2001-07-23 20:00 ` Linus Torvalds
2001-07-23 20:15 ` Jonathan Lundell
2001-07-23 22:51 ` Linus Torvalds
2001-07-24 3:45 ` Jonathan Lundell
2001-07-24 15:41 ` Davide Libenzi
2001-07-24 15:46 ` Alexander Viro
2001-07-24 16:01 ` Davide Libenzi
2001-07-24 16:08 ` Alexander Viro
2001-07-24 16:52 ` Davide Libenzi
2001-07-24 16:59 ` Linus Torvalds
2001-07-24 17:31 ` Davide Libenzi
2001-07-24 17:38 ` Linus Torvalds
2001-07-24 18:07 ` Anton Altaparmakov
2001-07-23 20:44 ` Chris Friesen
2001-07-23 21:11 ` Andrea Arcangeli
2001-07-23 21:50 ` Richard Gooch
2001-07-23 22:09 ` Andrea Arcangeli
2001-07-23 13:20 ` Rob Landley
2001-07-23 22:27 ` Andrea Arcangeli
2001-07-23 17:50 ` Rob Landley
2001-07-23 23:47 ` Richard Gooch
2001-07-24 0:04 ` Andrea Arcangeli
2001-07-24 9:02 ` Jan Hubicka
2001-07-24 15:35 ` Linus Torvalds
2001-07-24 16:04 ` Linus Torvalds
2001-07-25 22:49 ` Andrea Arcangeli
2001-07-25 23:16 ` Linus Torvalds
2001-07-25 23:37 ` Chris Friesen
2001-07-26 18:28 ` Jan Hubicka
2001-07-26 18:35 ` Alan Cox
2001-07-23 22:53 ` Linus Torvalds
2001-07-23 23:13 ` Alan Cox
2001-07-23 20:25 ` Jeff Dike
[not found] <no.id>
2001-07-23 20:57 ` Alan Cox
2001-07-23 21:14 ` Chris Friesen
2001-07-25 19:12 ` Alan Cox
2001-07-25 23:49 ` Alan Cox
2001-07-25 19:03 James W. Lake
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=20010723195055.A16919@athlon.random \
--to=andrea@suse.de \
--cc=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=user-mode-linux-user@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).