From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
akpm@linux-foundation.org
Cc: mcgrof@kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] umh: Optimize 'proc_cap_handler()'
Date: Sat, 11 Nov 2017 00:51:48 +0100 [thread overview]
Message-ID: <20171110235148.GW22894@wotan.suse.de> (raw)
In-Reply-To: <20171020193331.7233-1-christophe.jaillet@wanadoo.fr>
On Fri, Oct 20, 2017 at 09:33:31PM +0200, Christophe JAILLET wrote:
> If 'write' is 0, we can avoid a call to spin_lock/spin_unlock.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Thanks for the patch!
Acked-by: Luis R. Rodriguez <mcgrof@kernel.org>
I'll bounce a copy to Andrew for integration next.
Luis
> ---
> kernel/umh.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/umh.c b/kernel/umh.c
> index 6ff9905250ff..18e5fa4b0e71 100644
> --- a/kernel/umh.c
> +++ b/kernel/umh.c
> @@ -537,14 +537,14 @@ static int proc_cap_handler(struct ctl_table *table, int write,
> /*
> * Drop everything not in the new_cap (but don't add things)
> */
> - spin_lock(&umh_sysctl_lock);
> if (write) {
> + spin_lock(&umh_sysctl_lock);
> if (table->data == CAP_BSET)
> usermodehelper_bset = cap_intersect(usermodehelper_bset, new_cap);
> if (table->data == CAP_PI)
> usermodehelper_inheritable = cap_intersect(usermodehelper_inheritable, new_cap);
> + spin_unlock(&umh_sysctl_lock);
> }
> - spin_unlock(&umh_sysctl_lock);
>
> return 0;
> }
> --
> 2.14.1
>
>
--
Luis Rodriguez, SUSE LINUX GmbH
Maxfeldstrasse 5; D-90409 Nuernberg
prev parent reply other threads:[~2017-11-10 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 19:33 Christophe JAILLET
2017-11-08 1:02 ` Luis R. Rodriguez
2017-11-10 23:51 ` Luis R. Rodriguez [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=20171110235148.GW22894@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome