From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Convert BUG() to use unreachable()
Date: Thu, 17 Dec 2009 19:48:37 +0000 [thread overview]
Message-ID: <20091217194837.GD4440@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20091217193826.GE362@shareable.org>
On Thu, Dec 17, 2009 at 07:38:26PM +0000, Jamie Lokier wrote:
> Joe Buck wrote:
> > On Thu, Dec 17, 2009 at 11:06:13AM -0800, Russell King - ARM Linux wrote:
> > > On Thu, Dec 17, 2009 at 10:35:17AM -0800, Joe Buck wrote:
> > > > Besides, didn't I see a whole bunch of kernel security patches related
> > > > to null pointer dereferences lately? If page 0 can be mapped, you
> > > > suddenly won't get your trap.
> > >
> > > Page 0 can not be mapped on ARM kernels since the late 1990s, and this
> > > protection is independent of the generic kernel.
> > >
> > > Milage may vary on other architectures, but that's not a concern here.
>
> It does not trap on at least one ARM-nommu kernel...
I was going to say the following in a different reply but discarded it
because it wasn't relevant to the GCC list.
I regard ARM nommu as highly experimental, especially as the maintainer
vanished half way through merging it into mainline. I know that there
are some parts of ARM nommu that are highly buggy - such as ARM940
support invalidating the entire data cache on any DMA transaction...
say goodbye stacked return addresses.
As such, I would not be surprised if the ARM nommu kernel has _lots_ of
weird and wonderful bugs. I am not surprised that NULL pointer dereferences
don't work - its actually something I'd expect given that they have a
protection unit which the kernel doesn't apparently touch.
Maybe the protection unit code never got merged? I've no idea. As I
say, uclinux support got as far as being half merged and that's roughly
the state it's remained in ever since.
We don't even have any no-MMU configurations which the kernel builder
automatically tests for us.
Given the lack of progress/bug reporting on ARM uclinux, the lack of
platform support and the lack of configurations, my view is that there
is no one actually using it. I know that I don't particularly take any
care with respect to uclinux when making changes to the MMU based kernels.
Why bother if apparantly no one's using it?
next prev parent reply other threads:[~2009-12-17 19:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 9:55 [PATCH] ARM: Convert BUG() to use unreachable() Uwe Kleine-König
2009-12-10 17:50 ` Russell King - ARM Linux
[not found] ` <4B213627.5000007@caviumnetworks.com>
2009-12-16 13:58 ` Uwe Kleine-König
2009-12-17 15:01 ` Jamie Lokier
[not found] ` <4B2A65C6.7080009@caviumnetworks.com>
2009-12-17 17:17 ` Richard Guenther
2009-12-17 18:17 ` Russell King - ARM Linux
2009-12-17 18:35 ` Joe Buck
2009-12-17 19:06 ` Russell King - ARM Linux
2009-12-17 19:14 ` Joe Buck
2009-12-17 19:33 ` Russell King - ARM Linux
2009-12-17 19:38 ` Jamie Lokier
2009-12-17 19:48 ` Russell King - ARM Linux [this message]
2009-12-17 19:58 ` Russell King - ARM Linux
2009-12-17 19:04 ` Jamie Lokier
2009-12-21 19:30 ` Richard Henderson
2009-12-21 20:10 ` Russell King - ARM Linux
2009-12-22 14:09 ` Dave Korn
2009-12-22 14:12 ` Russell King - ARM Linux
2009-12-22 14:49 ` Dave Korn
2009-12-22 11:33 ` Paolo Bonzini
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=20091217194837.GD4440@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).