MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18161.27621.630048.643513@alkaid.it.uu.se>
Date: Wed, 19 Sep 2007 20:35:17 +0200
From: Mikael Pettersson <mikpe@it.uu.se>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Mikael Pettersson <mikpe@it.uu.se>, 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
In-Reply-To: <46F1475B.5050107@zytor.com>
References: <200709191454.l8JEsAQO010080@harpo.it.uu.se>
	<46F1475B.5050107@zytor.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 720
Lines: 17

H. Peter Anvin writes:
 > 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.

Indeed. My bad :-(
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/