All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Benjamin C.R. LaHaise" <blah@kvack.org>
Cc: Alexander Viro <viro@math.psu.edu>,
	"Stephen C. Tweedie" <sct@redhat.com>,
	Richard F Weber <rfweber@link.com>,
	linux-mm@kvack.org
Subject: Re: Hopefully a simple question on /proc/pid/mem
Date: Mon, 30 Apr 2001 22:58:02 +0100	[thread overview]
Message-ID: <20010430225802.H26638@redhat.com> (raw)
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

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/

  parent reply	other threads:[~2001-04-30 21:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-30 18:17 Hopefully a simple question on /proc/pid/mem Richard F Weber
2001-04-30 18:50 ` Stephen C. Tweedie
2001-04-30 19:00   ` Alexander Viro
2001-04-30 19:02     ` Benjamin C.R. LaHaise
2001-04-30 19:26       ` Alexander Viro
2001-04-30 19:26         ` Benjamin C.R. LaHaise
2001-04-30 19:44           ` Alexander Viro
2001-04-30 21:58       ` Stephen C. Tweedie [this message]
2001-05-01  1:13         ` Eric W. Biederman
2001-05-01  9:36           ` Stephen C. Tweedie
2001-05-01 15:16             ` Eric W. Biederman
2001-04-30 19:13   ` Richard F Weber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010430225802.H26638@redhat.com \
    --to=sct@redhat.com \
    --cc=blah@kvack.org \
    --cc=linux-mm@kvack.org \
    --cc=rfweber@link.com \
    --cc=viro@math.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.