[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Hopefully a simple question on /proc/pid/mem
- To: "Benjamin C.R. LaHaise" <blah@kvack.org>
- Subject: Re: Hopefully a simple question on /proc/pid/mem
- From: "Stephen C. Tweedie" <sct@redhat.com>
- Date: Mon, 30 Apr 2001 22:58:02 +0100
- Cc: Alexander Viro <viro@math.psu.edu>, "Stephen C. Tweedie" <sct@redhat.com>, Richard F Weber <rfweber@link.com>, linux-mm@kvack.org
- In-Reply-To: <Pine.LNX.3.96.1010430145934.30664D-100000@kanga.kvack.org>; from blah@kvack.org on Mon, Apr 30, 2001 at 03:02:40PM -0400
- References: <Pine.GSO.4.21.0104301457010.5737-100000@weyl.math.psu.edu> <Pine.LNX.3.96.1010430145934.30664D-100000@kanga.kvack.org>
- Sender: owner-linux-mm@kvack.org
- User-Agent: Mutt/1.2i
Hi,
On Mon, Apr 30, 2001 at 03:02:40PM -0400, Benjamin C.R. LaHaise wrote:
> On Mon, 30 Apr 2001, Alexander Viro wrote:
>
> > I wonder what's wrong with reading from /proc/<pid>/mem, though - it's
> > using the same code as ptrace.
>
> We can actually do this cleanly now that we have proper page_dirty
> semantics for raw io. The original reason for disabling /proc/*/mem was
> that it left big gaping holes in the mm code in 2.0, and it hasn't been
> repaired since.
It was mmap of /proc/*/mem which was busted. read/write should be OK.
Hint: think about what happens if you make a shared mapping of a
private proc/*/mem region...
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/