Re: [PATCH -mm] Don't truncate /proc/PID/environ at 4096 characters

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: [PATCH -mm] Don't truncate /proc/PID/environ at 4096 characters
    • From: Mikael Pettersson <[email protected]>
  • Re: [PATCH -mm] Don't truncate /proc/PID/environ at 4096 characters
    • From: "H. Peter Anvin" <[email protected]>
  • Re: [PATCH -mm] Don't truncate /proc/PID/environ at 4096 characters
    • From: Mikael Pettersson <[email protected]>

• Prev by Date: Re: [PATCH] Fix potential OOPS in generic_setlease()
• Next by Date: Re: 2.6.23-rc6-mm1
• Previous by thread: Re: [PATCH -mm] Don't truncate /proc/PID/environ at 4096 characters
• Next by thread: Re: [PATCH -mm] Don't truncate /proc/PID/environ at 4096 characters
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]