From: "Serge E. Hallyn" <serge@hallyn.com>
To: Kees Cook <keescook@chromium.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Solar Designer <solar@openwall.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
Andy Lutomirski <luto@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: Reorder inode_owner_or_capable() to avoid needless
Date: Tue, 20 Jun 2017 17:02:50 -0500 [thread overview]
Message-ID: <20170620220250.GA27180@mail.hallyn.com> (raw)
In-Reply-To: <20170620214024.GA121654@beast>
Quoting Kees Cook (keescook@chromium.org):
> Checking for capabilities should be the last operation when performing
> access control tests so that PF_SUPERPRIV is set only when it was required
> for success (implying that the capability was needed for the operation).
>
> Reported-by: Solar Designer <solar@openwall.com>
> Cc: Serge E. Hallyn <serge@hallyn.com>
Makes sense, thanks.
Acked-by: Serge Hallyn <serge@hallyn.com>
> Cc: Andy Lutomirski <luto@kernel.org>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> fs/inode.c | 2 +-
> fs/namei.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/inode.c b/fs/inode.c
> index db5914783a71..7092debe90cc 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -2023,7 +2023,7 @@ bool inode_owner_or_capable(const struct inode *inode)
> return true;
>
> ns = current_user_ns();
> - if (ns_capable(ns, CAP_FOWNER) && kuid_has_mapping(ns, inode->i_uid))
> + if (kuid_has_mapping(ns, inode->i_uid) && ns_capable(ns, CAP_FOWNER))
> return true;
> return false;
> }
> diff --git a/fs/namei.c b/fs/namei.c
> index 6571a5f5112e..efe53a5d0737 100644
> --- a/fs/namei.c
> +++ b/fs/namei.c
> @@ -1008,7 +1008,7 @@ static int may_linkat(struct path *link)
> /* Source inode owner (or CAP_FOWNER) can hardlink all they like,
> * otherwise, it must be a safe source.
> */
> - if (inode_owner_or_capable(inode) || safe_hardlink_source(inode))
> + if (safe_hardlink_source(inode) || inode_owner_or_capable(inode))
> return 0;
>
> audit_log_link_denied("linkat", link);
> --
> 2.7.4
>
>
> --
> Kees Cook
> Pixel Security
next prev parent reply other threads:[~2017-06-20 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 21:40 [PATCH] fs: Reorder inode_owner_or_capable() to avoid needless Kees Cook
2017-06-20 22:02 ` Serge E. Hallyn [this message]
2017-06-21 14:55 ` Andy Lutomirski
2017-06-30 0:06 ` Al Viro
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=20170620220250.GA27180@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=solar@openwall.com \
--cc=viro@zeniv.linux.org.uk \
/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).