From: David Howells <dhowells@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dhowells@redhat.com, "Serge E. Hallyn" <serue@us.ibm.com>,
Andreas Gruenbacher <agruen@suse.de>,
"Andrew G. Morgan" <morgan@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] file capabilities: Add no_file_caps switch
Date: Wed, 27 Aug 2008 18:00:07 +0100 [thread overview]
Message-ID: <27726.1219856407@redhat.com> (raw)
In-Reply-To: <20080827173236.2198786e@lxorguk.ukuu.org.uk>
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> That gets foul in another way - bounding the worst case RCU
> memory utilisation if someone is sitting doing things like while(1)
> change_credentials();
Is it worth calling synchronize_rcu() in commit_creds() to make sure that the
old memory will have been freed if possible? Admittedly that'll slow setuid()
and co. down, but it should avoid that problem.
David
next prev parent reply other threads:[~2008-08-27 17:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 18:57 [patch] file capabilities: Add no_file_caps switch Andreas Gruenbacher
2008-08-26 20:28 ` Ingo Molnar
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:13 ` David Howells
2008-08-27 16:32 ` Alan Cox
2008-08-27 17:00 ` David Howells [this message]
2008-08-27 16:57 ` Andreas Gruenbacher
2008-08-27 17:04 ` David Howells
2008-08-27 18:58 ` Serge E. Hallyn
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-28 15:35 ` Andrew G. Morgan
2008-08-28 17:09 ` Serge E. Hallyn
2008-08-28 16:27 ` Andreas Gruenbacher
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=27726.1219856407@redhat.com \
--to=dhowells@redhat.com \
--cc=agruen@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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