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

Mikael Pettersson wrote:
> 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,

Of course it does.  Address zero isn't typically mapped.

	-hpa
-
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: Mikael Pettersson <[email protected]>

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

Prev by Date: Re: [PATCH 2.6.23-rc6] NETWORKING : Edge Triggered EPOLLOUT events get missed for TCP sockets
Next by Date: Re: [patch 4/7] Immediate Values - i386 Optimization
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]