All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ptrace: fix ptrace_read_user for !CONFIG_MMU platforms
Date: Tue, 21 Feb 2012 11:35:48 +0000	[thread overview]
Message-ID: <20120221113548.GK22562@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120221105250.GC19696@mudshark.cambridge.arm.com>

On Tue, Feb 21, 2012 at 10:52:50AM +0000, Will Deacon wrote:
> On Tue, Feb 21, 2012 at 10:10:52AM +0000, Russell King - ARM Linux wrote:
> > On Tue, Feb 21, 2012 at 10:00:41AM +0000, Will Deacon wrote:
> > > On Tue, Feb 21, 2012 at 08:36:12AM +0000, Russell King - ARM Linux wrote:
> > > > Maybe no one uses a debugger for uclinux programs?
> > > 
> > > I confess to finding this by inspection rather than a debugging failure.
> > 
> > There is another explanation - that is no one in the uclinux world uses
> > mainline kernels, and this bug has been fixed ages ago in some uclinux
> > kernel tree.
> > 
> > That directly raises the question of the value of having the uclinux
> > baggage in the mainline kernel if no one is using mainline kernels for
> > uclinux work.  If the uclinux folk aren't willing to pass up bug fixes,
> > then having it in mainline is, frankly, a waste of space.
> 
> I know the validation guys in ARM use mainline kernels for bringup on
> MMU-less CPUs (ok, they have extra patches on top but these tend to be
> platform-specific hacks since they're running on an RTL emulator. Plus they do
> periodically rebase onto new release kernels.). Debugging tends to be at a
> much lower level than GDB can provide though (i.e. waveforms), so this would
> have gone un-noticed.
> 
> I think it's worth keeping the support, particularly in light of the recent
> interest in M-class CPUs on the list.

In any case, I think we need to know whether this really is a problem or
not.  If no one has noticed that this is broken in the last 2.5 years,
that implies that no one is using this, and so there's no point either
the kernel or gdb carrying support which no one is using.

The other thing is, as this has been broken right from the start, has
gdb under uclinux even been tested?

I don't think fixing this in mainline until we know the full story behind
this is the right thing to be doing.  There's no point fixing a feature
which no one's using.

  reply	other threads:[~2012-02-21 11:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 18:37 [PATCH] ARM: ptrace: fix ptrace_read_user for !CONFIG_MMU platforms Will Deacon
2012-02-20 19:46 ` Russell King - ARM Linux
2012-02-21  1:24   ` Paul Brook
2012-02-21  8:36     ` Russell King - ARM Linux
2012-02-21 10:00       ` Will Deacon
2012-02-21 10:10         ` Russell King - ARM Linux
2012-02-21 10:52           ` Will Deacon
2012-02-21 11:35             ` Russell King - ARM Linux [this message]
2012-02-21 13:22               ` Will Deacon
2012-02-24 14:36                 ` Will Deacon
2012-02-24 18:16                   ` Russell King - ARM Linux
2012-02-29 18:52                     ` Will Deacon
2012-03-26 12:43                       ` Will Deacon
2012-02-22  1:33           ` Greg Ungerer

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=20120221113548.GK22562@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 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.