From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH 5/5] Use seek+read instead of pread to read from /dev/$$/mem files.
Date: Fri, 09 Oct 2015 15:44:52 +0200 [thread overview]
Message-ID: <1444398292.25287.146.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: 87fv1k1g9c.fsf@oracle.com
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
On Fri, 2015-10-09 at 12:35 +0200, Jose E. Marchesi wrote:
> Here you go.
>
> commit 43f68c295e60ca716bc5d1a3876c62f949d4f889
> Author: Jose E. Marchesi <jose.marchesi@oracle.com>
> Date: Fri Oct 9 06:38:39 2015 -0400
>
> Use seek+read instead of pread to read from /dev/$$/mem files.
>
> pread[64] always returns EINVAL when negative offsets are used.
> read+seek allows us to read in-memory vdso objects mapped high in the
> address space.
>
> Signed-off-by: Jose E. Marchesi <jose.marchesi@oracle.com>
Looks good. Thanks. Pushed to master.
next reply other threads:[~2015-10-09 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 13:44 Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-09 10:35 Jose E. Marchesi
2015-10-05 22:33 Mark Wielaard
2015-10-05 15:36 Jose E. Marchesi
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=1444398292.25287.146.camel@bordewijk.wildebeest.org \
--to=mjw@redhat.com \
--cc=elfutils-devel@lists.fedorahosted.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 read-only IMAP folder(s) and NNTP newsgroup(s).