From: "Serge E. Hallyn" <serge@hallyn.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, serge@hallyn.com
Cc: Jari Ruusu <jariruusu@users.sourceforge.net>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Alistair Delva <adelva@google.com>,
Khazhismel Kumykov <khazhy@google.com>,
Bart Van Assche <bvanassche@acm.org>,
Serge Hallyn <serge@hallyn.com>, Jens Axboe <axboe@kernel.dk>,
Paul Moore <paul@paul-moore.com>,
selinux@vger.kernel.org, linux-security-module@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH 5.10 130/154] block: Check ADMIN before NICE for IOPRIO_CLASS_RT
Date: Wed, 24 Nov 2021 11:33:11 -0600 [thread overview]
Message-ID: <20211124173310.GA12039@mail.hallyn.com> (raw)
In-Reply-To: <YZ5ayhuOMZwkd9j6@kroah.com>
On Wed, Nov 24, 2021 at 04:31:22PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Nov 24, 2021 at 04:22:50PM +0200, Jari Ruusu wrote:
> > Greg Kroah-Hartman wrote:
> > > From: Alistair Delva <adelva@google.com>
> > >
> > > commit 94c4b4fd25e6c3763941bdec3ad54f2204afa992 upstream.
> > [SNIP]
> > > --- a/block/ioprio.c
> > > +++ b/block/ioprio.c
> > > @@ -69,7 +69,14 @@ int ioprio_check_cap(int ioprio)
> > >
> > > switch (class) {
> > > case IOPRIO_CLASS_RT:
> > > - if (!capable(CAP_SYS_NICE) && !capable(CAP_SYS_ADMIN))
> > > + /*
> > > + * Originally this only checked for CAP_SYS_ADMIN,
> > > + * which was implicitly allowed for pid 0 by security
> > > + * modules such as SELinux. Make sure we check
> > > + * CAP_SYS_ADMIN first to avoid a denial/avc for
> > > + * possibly missing CAP_SYS_NICE permission.
> > > + */
> > > + if (!capable(CAP_SYS_ADMIN) && !capable(CAP_SYS_NICE))
> > > return -EPERM;
> > > fallthrough;
> > > /* rt has prio field too */
> >
> > What exactly is above patch trying to fix?
> > It does not change control flow at all, and added comment is misleading.
>
> See the thread on the mailing list for what it does and why it is
> needed.
>
> It does change the result when selinux is enabled.
>
> thanks,
>
> greg k-h
The case where we create a newer more fine grained capability which is a
sub-cap of a broader capability like CAP_SYS_ADMIN is analogous. See
check_syslog_permissions() for instance.
So I think a helper like
int capable_either_or(int cap1, int cap2) {
if (has_capability_noaudit(current, cap1))
return 0;
return capable(cap2);
}
might be worthwhile.
next prev parent reply other threads:[~2021-11-24 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211124115702.361983534@linuxfoundation.org>
2021-11-24 11:58 ` [PATCH 5.10 130/154] block: Check ADMIN before NICE for IOPRIO_CLASS_RT Greg Kroah-Hartman
2021-11-24 14:22 ` Jari Ruusu
2021-11-24 15:31 ` Greg Kroah-Hartman
2021-11-24 17:33 ` Serge E. Hallyn [this message]
2021-11-24 18:15 ` Greg Kroah-Hartman
2021-11-24 18:34 ` Christian Göttsche
2021-11-24 23:30 ` Serge E. Hallyn
2021-11-24 23:29 ` Serge E. Hallyn
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=20211124173310.GA12039@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=adelva@google.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=jariruusu@users.sourceforge.net \
--cc=kernel-team@android.com \
--cc=khazhy@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).