From: Daniel Jacobowitz <drow@false.org>
To: Andreas Schwab <schwab@suse.de>
Cc: David Lecomber <david@lecomber.net>, gdb <gdb@sources.redhat.com>
Subject: Re: Whacky ia64: linux_proc_xfer_partial and lseek vs pread64
Date: Fri, 10 Feb 2006 19:06:00 -0000 [thread overview]
Message-ID: <20060210190617.GA30740@nevyn.them.org> (raw)
In-Reply-To: <jewtg3m43c.fsf@sykes.suse.de>
On Fri, Feb 10, 2006 at 08:00:23PM +0100, Andreas Schwab wrote:
> Daniel Jacobowitz <drow@false.org> writes:
>
> > On Fri, Feb 10, 2006 at 07:04:51PM +0100, Andreas Schwab wrote:
> >> pread and lseek with SEEK_SET do not allow negative offsets. lseek on
> >> /proc/$$/mem is a special exception.
> >
> > Uh-oh. Should pread have the same exception, or must we fall back to
> > lseek?
>
> pread fails upfront with offset < 0, whereas lseek lets the filesystem
> llseek function decide. But a fallback wouldn't help here anyway, because
> you can't read the vdso memory with read, only with ptrace.
Fascinating. That definitely seems like a kernel bug to me; why not?
I see some magic bits in the kernel ptrace support to read backing
stores, which are obviously going to get fouled up by pread support.
But I don't see anything that would affect the vDSO.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-10 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 17:15 David Lecomber
2006-02-10 17:24 ` Daniel Jacobowitz
2006-02-10 18:05 ` Andreas Schwab
2006-02-10 18:14 ` Daniel Jacobowitz
2006-02-10 19:00 ` Andreas Schwab
2006-02-10 19:06 ` Daniel Jacobowitz [this message]
2006-02-11 16:22 ` Andreas Schwab
2006-02-11 16:50 ` Andreas Schwab
2006-02-11 18:26 ` Daniel Jacobowitz
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=20060210190617.GA30740@nevyn.them.org \
--to=drow@false.org \
--cc=david@lecomber.net \
--cc=gdb@sources.redhat.com \
--cc=schwab@suse.de \
/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