From: Ingo Molnar <mingo@elte.hu>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: "Andrew G. Morgan" <morgan@kernel.org>,
Serge Hallyn <serue@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] file capabilities: Add no_file_caps switch
Date: Tue, 26 Aug 2008 22:28:32 +0200 [thread overview]
Message-ID: <20080826202832.GB16072@elte.hu> (raw)
In-Reply-To: <200808262057.51606.agruen@suse.de>
* Andreas Gruenbacher <agruen@suse.de> wrote:
> +++ b/kernel/sched.c
> @@ -8149,6 +8149,15 @@ void __init sched_init(void)
> plist_head_init(&init_task.pi_waiters, &init_task.pi_lock);
> #endif
>
> +#ifdef CONFIG_SECURITY_FILE_CAPABILITIES
> + /*
> + * Because of the reduced scope of CAP_SETPCAP when filesystem
> + * capabilities are in effect, it is safe to allow CAP_SETPCAP to
> + * be available in the default configuration.
> + */
> + init_task.cap_bset = CAP_FULL_SET;
> +#endif
hm, this doesnt belong into sched.c. You need your own (ifdef-less) init
function in init/main.c or so.
Ingo
next prev parent reply other threads:[~2008-08-26 20:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 18:57 Andreas Gruenbacher
2008-08-26 20:28 ` Ingo Molnar [this message]
2008-08-27 13:52 ` Serge E. Hallyn
2008-08-27 15:29 ` Andreas Gruenbacher
2008-08-27 16:04 ` Serge E. Hallyn
2008-08-27 16:57 ` Andreas Gruenbacher
2008-08-27 18:58 ` Serge E. Hallyn
2008-08-28 15:35 ` Andrew G. Morgan
2008-08-28 17:09 ` Serge E. Hallyn
2008-08-28 16:27 ` Andreas Gruenbacher
2008-08-27 21:14 ` David Howells
2008-08-28 0:05 ` James Morris
2008-08-28 0:48 ` Serge E. Hallyn
2008-08-28 1:57 ` James Morris
2008-08-27 17:04 ` David Howells
2008-08-27 16:13 ` David Howells
2008-08-27 16:32 ` Alan Cox
2008-08-27 17:00 ` David Howells
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=20080826202832.GB16072@elte.hu \
--to=mingo@elte.hu \
--cc=agruen@suse.de \
--cc=linux-kernel@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®