From: Hugh Dickins <hugh@veritas.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
james-p@moving-picture.com, linux-kernel@vger.kernel.org,
aarapov@redhat.com, akpm@linux-foundation.org
Subject: Re: [PATCH -mm] Don't truncate /proc/PID/environ at 4096 characters
Date: Wed, 19 Sep 2007 20:29:07 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709192023580.13121@blonde.wat.veritas.com> (raw)
In-Reply-To: <18161.27621.630048.643513@alkaid.it.uu.se>
On Wed, 19 Sep 2007, Mikael Pettersson wrote:
> H. Peter Anvin writes:
> > Mikael Pettersson wrote:
> > > Does /proc/PID/mem even work? If I do `strace cat /proc/PID/mem > /dev/null'
> > > for a known good PID, the first read() from /proc/PID/mem fails with ESRCH,
> >
> > Of course it does. Address zero isn't typically mapped.
>
> Indeed. My bad :-(
No, not quite. Peter explains why "cat /proc/self/mem" gets EIO,
but you were seeing "cat /proc/other/mem" get ESRCH: that's from
the stringent !MAY_PTRACE || !ptrace_may_attach checks.
Hugh
next prev parent reply other threads:[~2007-09-19 19:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 14:54 Mikael Pettersson
2007-09-19 15:59 ` H. Peter Anvin
2007-09-19 18:35 ` Mikael Pettersson
2007-09-19 19:29 ` Hugh Dickins [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-25 16:44 James Pearson
2007-09-19 13:35 James Pearson
2007-09-20 23:46 ` Andrew Morton
2007-09-21 9:41 ` James Pearson
2007-09-21 10:00 ` Mel Gorman
2007-09-21 1:56 ` Arvin Moezzi
2007-09-21 9:47 ` James Pearson
2007-09-21 12:47 ` Arvin Moezzi
2007-09-21 13:47 ` James Pearson
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=Pine.LNX.4.64.0709192023580.13121@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=aarapov@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=james-p@moving-picture.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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
all inboxes | Powered by JetHome®