mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	linux-security-module@vger.kernel.org,
	James Morris <jmorris@redhat.com>,
	Andrew Morgan <morgan@kernel.org>,
	Andreas Gruenbacher <agruen@suse.de>,
	Andrew Morton <akpm@osdl.org>, Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 1/2] file capabilities: add no_file_caps switch (v2)
Date: Mon, 22 Sep 2008 15:57:33 -0700	[thread overview]
Message-ID: <20080922225733.GB610@sequoia.sous-sol.org> (raw)
In-Reply-To: <20080922184835.GA2826@us.ibm.com>

* Serge E. Hallyn (serue@us.ibm.com) wrote:
> --- a/kernel/capability.c
> +++ b/kernel/capability.c
> @@ -33,6 +33,19 @@ EXPORT_SYMBOL(__cap_empty_set);
>  EXPORT_SYMBOL(__cap_full_set);
>  EXPORT_SYMBOL(__cap_init_eff_set);
>  
> +#ifdef CONFIG_SECURITY_FILE_CAPABILITIES
> +int file_caps_enabled = 1;
> +
> +static int __init file_caps_disable(char *str)
> +{
> +	file_caps_enabled = 0;
> +	return 1;
> +}
> +__setup("no_file_caps", file_caps_disable);
> +#else
> +static const int file_caps_enabled = 0;
> +#endif

> --- a/security/commoncap.c
> +++ b/security/commoncap.c
> @@ -27,6 +27,12 @@
>  #include <linux/prctl.h>
>  #include <linux/securebits.h>
>  
> +#ifdef CONFIG_SECURITY_FILE_CAPABILITIES
> +extern int file_caps_enabled;
> +#else
> +static const int file_caps_enabled = 0;
> +#endif
> +

file_caps_enabled cut 'n paste mistake when !CONFIG_SECURITY_FILE_CAPABILITIES?

Also, plan to update Documentation/kernel-parameters.txt?

thanks,
-chris

  parent reply	other threads:[~2008-09-22 23:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 18:48 Serge E. Hallyn
2008-09-22 18:49 ` [PATCH 2/2] file capabilities: turn on by default Serge E. Hallyn
2008-09-22 19:03   ` Randy Dunlap
2008-09-22 19:56     ` Serge E. Hallyn
2008-09-22 21:09       ` Randy Dunlap
2008-09-22 22:53       ` Chris Wright
2008-09-22 19:16 ` [PATCH 1/2] file capabilities: add no_file_caps switch (v2) Stephen Smalley
2008-09-22 20:09   ` Andreas Gruenbacher
2008-09-22 21:50     ` Serge E. Hallyn
2008-09-22 22:08       ` Andreas Gruenbacher
2008-09-23  6:48       ` James Morris
2008-09-22 22:57 ` Chris Wright [this message]
2008-09-23 15:51   ` Serge E. Hallyn
     [not found] <beYE7-1Xc-41@gated-at.bofh.it>
     [not found] ` <beZ72-2GM-5@gated-at.bofh.it>
     [not found]   ` <bf035-3Tp-5@gated-at.bofh.it>
2008-09-23  7:21     ` Markku Savela
  -- strict thread matches above, loose matches on Subject: below --
2008-08-28 19:54 Serge Hallyn
2008-08-29  0:35 ` Andrew G. Morgan

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=20080922225733.GB610@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=agruen@suse.de \
    --cc=akpm@osdl.org \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=morgan@kernel.org \
    --cc=serue@us.ibm.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

all inboxes | Powered by JetHome®