From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ptrace: fix ptrace_read_user for !CONFIG_MMU platforms
Date: Tue, 21 Feb 2012 10:00:41 +0000 [thread overview]
Message-ID: <20120221100041.GA19696@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20120221083612.GG22562@n2100.arm.linux.org.uk>
On Tue, Feb 21, 2012 at 08:36:12AM +0000, Russell King - ARM Linux wrote:
> On Tue, Feb 21, 2012 at 01:24:22AM +0000, Paul Brook wrote:
> > I suspect I submitted the original patch. I don't remember the details, but
> > it definitely worked at the time. IIRC some other targets (m68k?) used an
> > even less palatable hack.
>
> I don't believe that - looking at the history in git, since it was merged
> the code has been:
>
> static int ptrace_read_user(struct task_struct *tsk, unsigned long off,
> unsigned long __user *ret)
> {
> unsigned long tmp;
>
> if (off & 3 || off >= sizeof(struct user))
> return -EIO;
>
> tmp = 0;
> if (off == PT_TEXT_ADDR)
> tmp = tsk->mm->start_code;
> else if (off == PT_DATA_ADDR)
> tmp = tsk->mm->start_data;
> else if (off == PT_TEXT_END_ADDR)
> tmp = tsk->mm->end_code;
> else if (off < sizeof(struct pt_regs))
> tmp = get_user_reg(tsk, off >> 2);
>
> And since PT_TEXT_ADDR is 0x10000, this will fail with -EIO. So, there's
> no way this could have been used successfully in the last 2.5 years.
Agreed, it does seem that this would always have failed, however a quick look
at GDB also suggests that it would at least try to access these guys on an
MMU-less system.
> Maybe no one uses a debugger for uclinux programs?
I confess to finding this by inspection rather than a debugging failure.
Will
next prev parent reply other threads:[~2012-02-21 10:00 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 [this message]
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
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=20120221100041.GA19696@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--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).