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

On Wed, 19 Sep 2007 14:35:29 +0100, James Pearson wrote:
> /proc/PID/environ currently truncates at 4096 characters, patch based on 
> the /proc/PID/mem code.

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,
which is bullocks. cat /proc/PID/environ does work. I'm seeing this on
2.6.22 vanilla, 2.6.20 FC6, and 2.6.18 RHEL5 kernels.

/Mikael
-
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/

---

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

• Prev by Date: [PATCH] x86: also show non-zero IRQ counts for vectors that currently don't have a handler
• Next by Date: [PATCH 1/2] strip generated symbols from *.ko
• 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]