From: "Serge E. Hallyn" <serue@us.ibm.com>
To: linux-security-module@vger.kernel.org
Cc: Steve Grubb <sgrubb@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
Kees Cook <kees.cook@canonical.com>,
Andrew Morgan <morgan@kernel.org>,
Andreas Gruenbacher <agruen@suse.de>,
Michael Kerrisk <mtk.manpages@gmail.com>,
George Wilson <gcwilson@us.ibm.com>,
KaiGai Kohei <kaigai@kaigai.gr.jp>
Subject: Re: [RFC] remove CONFIG_SECURITY_FILE_CAPABILITIES compile option
Date: Fri, 20 Nov 2009 14:26:16 -0600 [thread overview]
Message-ID: <20091120202616.GA17091@us.ibm.com> (raw)
In-Reply-To: <20091120201933.GA16694@us.ibm.com>
Quoting Serge E. Hallyn (serue@us.ibm.com):
> @@ -457,10 +429,8 @@ static inline int get_file_caps(struct linux_binprm *bprm, bool *effective)
> */
> static inline int cap_limit_ptraced_target(void)
> {
> -#ifndef CONFIG_SECURITY_FILE_CAPABILITIES
> if (capable(CAP_SETPCAP))
> return 0;
> -#endif
Gah. Will fix, of course, but general question/rfc still stands.
-serge
prev parent reply other threads:[~2009-11-20 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 20:19 [RFC] remove CONFIG_SECURITY_FILE_CAPABILITIES compile option Serge E. Hallyn
2009-11-20 20:26 ` Serge E. Hallyn [this message]
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=20091120202616.GA17091@us.ibm.com \
--to=serue@us.ibm.com \
--cc=agruen@suse.de \
--cc=gcwilson@us.ibm.com \
--cc=kaigai@kaigai.gr.jp \
--cc=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=sgrubb@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