From: Jake Edge <jake@lwn.net>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
Eric Paris <eparis@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Roland McGrath <roland@redhat.com>,
mingo@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: avoid leaking eip, esp, or wchan to non-privileged processes (fwd)
Date: Sun, 3 May 2009 19:11:24 -0600 [thread overview]
Message-ID: <20090503191124.27b3bf45@chukar> (raw)
In-Reply-To: <alpine.LRH.2.00.0905040917240.20251@tundra.namei.org>
On Mon, 4 May 2009 09:27:29 +1000 (EST) James Morris wrote:
> This patch needs some review.
Indeed.
> Note that stable@kernel.org typically backport already-reviewed and
> applied patches. I think security@kernel.org is for reporting
> problems in a non-public way (whereas, this is already public
> knowledge).
I realize (now :) that I didn't get this out to all of the right folks,
thanks for doing that. I didn't realize security@kernel.org was only
for non-public security problems, though. Maybe there needs to be a
'security maintainer' separate from that list? Or maybe there is one
and I just didn't find that person in MAINTAINERS?
It would seem that the 'start_stack' value output by /proc/pid/stat
should also only be available to processes that can ptrace ... that was
not part of my original patch, but I think should be added ...
jake
--
Jake Edge - LWN - jake@lwn.net - http://lwn.net
next prev parent reply other threads:[~2009-05-04 1:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 23:27 [PATCH] proc: avoid leaking eip, esp, or wchan to non-privileged processes (fwd) James Morris
2009-05-03 23:58 ` Arjan van de Ven
2009-05-04 1:11 ` Jake Edge [this message]
2009-05-04 14:38 ` Greg KH
2009-05-04 6:09 ` Eric W. Biederman
2009-05-04 13:22 ` Jake Edge
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=20090503191124.27b3bf45@chukar \
--to=jake@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=roland@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