From: "Christian Göttsche" <cgzones@googlemail.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: SElinux list <selinux@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] security: keys: perform capable check only on privileged operations
Date: Tue, 18 Jul 2023 17:32:32 +0200 [thread overview]
Message-ID: <CAJ2a_Dd-piQ51dqptuhJ8pXm+4HrFAcdbA-ESd8YwNO3qHnJrA@mail.gmail.com> (raw)
On Wed, 2023-05-21 at 02:04 +0300, Jarkko Sakkinen wrote:
> On Thu, 2023-05-25 at 17:25 -0400, Paul Moore wrote:
> > > A minor inconvenience is the number of needed arguments (and the
> > > actual code after inlining should be the same to the inner scope in
> > > the end).
> >
> > Well, lucky for you, Jarkko and David maintain the keys code, not me,
> > and Jarkko seems to like your patch just fine :)
> >
> > Jarkko, I assume you'll be taking this via the keys tree?
>
> I just picked it and mirrored to linux-next.
>
> I think it is super important change because it tones down the human
> error (a little bit at least). You could say improves user experience
> kind of I guess :-)
>
> BR, Jarkko
Kindly ping; I do not see this patch applied anywhere.
Regards,
Christian
next reply other threads:[~2023-07-18 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 15:32 Christian Göttsche [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-11 12:32 [PATCH] security: keys: perform capable check only on privileged operations Christian Göttsche
2023-05-19 21:07 ` Paul Moore
2023-05-23 18:33 ` Christian Göttsche
2023-05-25 21:25 ` Paul Moore
2023-05-30 23:04 ` Jarkko Sakkinen
2023-05-23 19:31 ` Jarkko Sakkinen
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=CAJ2a_Dd-piQ51dqptuhJ8pXm+4HrFAcdbA-ESd8YwNO3qHnJrA@mail.gmail.com \
--to=cgzones@googlemail.com \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).