From: Alexander Viro <viro@math.psu.edu>
To: "Benjamin C.R. LaHaise" <blah@kvack.org>
Cc: "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 15:44:32 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.21.0104301532130.5737-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <Pine.LNX.3.96.1010430152401.30664E-100000@kanga.kvack.org>
On Mon, 30 Apr 2001, Benjamin C.R. LaHaise wrote:
> On Mon, 30 Apr 2001, Alexander Viro wrote:
>
> > ITYM "disabling _write_ on /proc/*/mem". Read is OK. Anyway, current
> > mem_write() uses the same code as PTRACE_POKEDATA, so if the latter works,
> > the former also should be OK.
>
> Actually, even read on /proc/*/mem caused problems in 2.0: the elevated
> usage could would prevent memory from being reclaimed by the swapper
> properly. Things are so much better now it's not even funny.
ISTR removing some rather nasty code during the procfs rewrite. From
mem_read() and mem_write() - basically, made them wrappers around
access_process_vm().
--
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/
next prev parent reply other threads:[~2001-04-30 19:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 18:17 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 [this message]
2001-04-30 21:58 ` Stephen C. Tweedie
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=Pine.GSO.4.21.0104301532130.5737-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--cc=blah@kvack.org \
--cc=linux-mm@kvack.org \
--cc=rfweber@link.com \
--cc=sct@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox