From: Oleg Nesterov <oleg@redhat.com>
To: WANG Cong <xiyou.wangcong@gmail.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: + proc-clean-up-proc-pid-environ-handling.patch added to -mm tree
Date: Wed, 8 Feb 2012 16:15:16 +0100 [thread overview]
Message-ID: <20120208151516.GA15570@redhat.com> (raw)
> From: Cong Wang <xiyou.wangcong@gmail.com>
> Subject: proc: clean up /proc/<pid>/environ handling
>
> Similar to e268337dfe2 ("proc: clean up and fix /proc/<pid>/mem
> handling"),
and has the same problem,
> move the check of permission to open(), this will simplify
> read() code.
but allows to kill the system trivially.
Please look at 6d08f2c7139790c268820a2e590795cb8333181a
"proc: make sure mem_open() doesn't pin the target's memory"
Oleg.
next reply other threads:[~2012-02-08 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 15:15 Oleg Nesterov [this message]
2012-02-10 3:09 ` + proc-clean-up-proc-pid-environ-handling.patch added to -mm tree Cong Wang
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=20120208151516.GA15570@redhat.com \
--to=oleg@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).