From: Frederick Lawler <fred@cloudflare.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-aio@kvack.org, linux-fsdevel@vger.kernel.org,
linux-cachefs@redhat.com, linux-cifs@vger.kernel.org,
samba-technical@lists.samba.org, linux-mm@kvack.org,
linux-nfs@vger.kernel.org, linux-unionfs@vger.kernel.org,
linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
keyrings@vger.kernel.org, selinux@vger.kernel.org,
serge@hallyn.com, amir73il@gmail.com, kernel-team@cloudflare.com,
Jeff Moyer <jmoyer@redhat.com>, Paul Moore <paul@paul-moore.com>
Subject: Re: [PATCH v3] cred: Propagate security_prepare_creds() error code
Date: Mon, 13 Jun 2022 08:46:49 -0500 [thread overview]
Message-ID: <b4113083-73de-3ab6-e23f-32c6627d177e@cloudflare.com> (raw)
In-Reply-To: <YqJ/0W3wxPThWqgC@sol.localdomain>
Hi Eric,
On 6/9/22 6:18 PM, Eric Biggers wrote:
> On Wed, Jun 08, 2022 at 10:09:42AM -0500, Frederick Lawler wrote:
>> diff --git a/fs/aio.c b/fs/aio.c
>> index 3c249b938632..5abbe88c3ca7 100644
>> --- a/fs/aio.c
>> +++ b/fs/aio.c
>> @@ -1620,6 +1620,8 @@ static void aio_fsync_work(struct work_struct *work)
>> static int aio_fsync(struct fsync_iocb *req, const struct iocb *iocb,
>> bool datasync)
>> {
>> + int err;
>> +
>> if (unlikely(iocb->aio_buf || iocb->aio_offset || iocb->aio_nbytes ||
>> iocb->aio_rw_flags))
>> return -EINVAL;
>> @@ -1628,8 +1630,11 @@ static int aio_fsync(struct fsync_iocb *req, const struct iocb *iocb,
>> return -EINVAL;
>>
>> req->creds = prepare_creds();
>> - if (!req->creds)
>> - return -ENOMEM;
>> + if (IS_ERR(req->creds)) {
>> + err = PTR_ERR(req->creds);
>> + req->creds = NULL;
>> + return err;
>> + }
>
> This part is a little ugly. How about doing:
>
> creds = prepare_creds();
> if (IS_ERR(creds))
> return PTR_ERR(creds);
> req->creds = creds;
>
I can do that, and same for below.
>> diff --git a/fs/exec.c b/fs/exec.c
>> index 0989fb8472a1..02624783e40e 100644
>> --- a/fs/exec.c
>> +++ b/fs/exec.c
>> @@ -1468,15 +1468,19 @@ EXPORT_SYMBOL(finalize_exec);
>> */
>> static int prepare_bprm_creds(struct linux_binprm *bprm)
>> {
>> + int err = -ERESTARTNOINTR;
>> if (mutex_lock_interruptible(¤t->signal->cred_guard_mutex))
>> - return -ERESTARTNOINTR;
>> + return err;
>>
>> bprm->cred = prepare_exec_creds();
>> - if (likely(bprm->cred))
>> - return 0;
>> + if (IS_ERR(bprm->cred)) {
>> + err = PTR_ERR(bprm->cred);
>> + bprm->cred = NULL;
>> + mutex_unlock(¤t->signal->cred_guard_mutex);
>> + return err;
>> + }
>>
>> - mutex_unlock(¤t->signal->cred_guard_mutex);
>> - return -ENOMEM;
>> + return 0;
>> }
>
> Similarly:
>
> static int prepare_bprm_creds(struct linux_binprm *bprm)
> {
> struct cred *cred;
>
> if (mutex_lock_interruptible(¤t->signal->cred_guard_mutex))
> return -ERESTARTNOINTR;
>
> cred = prepare_exec_creds();
> if (IS_ERR(cred)) {
> mutex_unlock(¤t->signal->cred_guard_mutex);
> return PTR_ERR(cred);
> }
> bprm->cred = cred;
> return 0;
> }
>
>> diff --git a/kernel/nsproxy.c b/kernel/nsproxy.c
>> index eec72ca962e2..6cf75aa83b6c 100644
>> --- a/kernel/nsproxy.c
>> +++ b/kernel/nsproxy.c
>> @@ -311,6 +311,7 @@ static void put_nsset(struct nsset *nsset)
>>
>> static int prepare_nsset(unsigned flags, struct nsset *nsset)
>> {
>> + int err = -ENOMEM;
>> struct task_struct *me = current;
>>
>> nsset->nsproxy = create_new_namespaces(0, me, current_user_ns(), me->fs);
>> @@ -324,6 +325,12 @@ static int prepare_nsset(unsigned flags, struct nsset *nsset)
>> if (!nsset->cred)
>> goto out;
>>
>> + if (IS_ERR(nsset->cred)) {
>> + err = PTR_ERR(nsset->cred);
>> + nsset->cred = NULL;
>> + goto out;
>> + }
>
> Why is the NULL check above being kept?
>
In the branch prior:
if (flags & CLONE_NEWUSER) {
nsset->cred = prepare_creds();
else
nsset->cred = current_cred();
I don't see cases where others are checking for null after
current_cred(), therefore I can remove that check.
> Also, drivers/crypto/ccp/sev-dev.c needs to be updated.
>
Nice catch! I clearly missed addition after the merge window.
> - Eric
next prev parent reply other threads:[~2022-06-13 15:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 15:09 [PATCH v3] cred: Propagate security_prepare_creds() error code Frederick Lawler
2022-06-09 23:18 ` Eric Biggers
2022-06-13 13:46 ` Frederick Lawler [this message]
2022-06-13 17:04 ` Eric W. Biederman
2022-06-13 20:52 ` Frederick Lawler
2022-06-14 4:44 ` Eric W. Biederman
2022-06-14 14:39 ` Casey Schaufler
2022-06-14 16:06 ` Frederick Lawler
2022-06-14 16:30 ` Eric W. Biederman
2022-06-14 18:59 ` Frederick Lawler
2022-06-15 10:30 ` Christian Brauner
2022-06-15 14:14 ` Paul Moore
2022-06-15 15:06 ` Ignat Korchagin
2022-06-15 15:33 ` Paul Moore
2022-06-15 15:55 ` Casey Schaufler
2022-06-16 15:04 ` Frederick Lawler
2022-06-15 15:30 ` Casey Schaufler
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=b4113083-73de-3ab6-e23f-32c6627d177e@cloudflare.com \
--to=fred@cloudflare.com \
--cc=amir73il@gmail.com \
--cc=ebiggers@kernel.org \
--cc=jmoyer@redhat.com \
--cc=kernel-team@cloudflare.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-aio@kvack.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=samba-technical@lists.samba.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 NNTP newsgroup(s).