From: "Mickaël Salaün" <mic@digikod.net>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
Paul Moore <paul@paul-moore.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org,
Jan Kara <jack@suse.cz>, Tahera Fahimi <fahimitahera@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Casey Schaufler <casey@schaufler-ca.com>,
James Morris <jmorris@namei.org>, Jann Horn <jannh@google.com>,
Ondrej Mosnacek <omosnace@redhat.com>,
"Serge E . Hallyn" <serge@hallyn.com>,
Stephen Smalley <stephen.smalley.work@gmail.com>
Subject: Re: [PATCH v2] fs,security: Fix file_set_fowner LSM hook inconsistencies
Date: Tue, 13 Aug 2024 12:09:19 +0200 [thread overview]
Message-ID: <20240813.iidaejohj5Oo@digikod.net> (raw)
In-Reply-To: <o6ptrfa7gjdukphqtp6dakq3ykndrjusuhi4fyvpc5ne6amcig@lqbdb2dg7yzv>
On Mon, Aug 12, 2024 at 11:45:29PM +0200, Mateusz Guzik wrote:
> On Mon, Aug 12, 2024 at 07:44:17PM +0200, Mickaël Salaün wrote:
>
> No opinion about the core idea, I'll note though that this conflicts
> with a patch to move f_owner out of the struct:
> https://lore.kernel.org/linux-fsdevel/20240809-koriander-biobauer-6237cbc106f3@brauner/
Thanks for the heads-up.
>
> Presumably nothing which can't get sorted out with some shoveling.
>
> I do have actionable remark concerning creds though: both get_cred and
> put_cred are slow. Sorting that out is on my todo list.
>
> In the meantime adding more calls can be avoided:
OK, I'll add that in the next version.
>
> > diff --git a/fs/file_table.c b/fs/file_table.c
> > index 4f03beed4737..d28b76aef4f3 100644
> > --- a/fs/file_table.c
> > +++ b/fs/file_table.c
> > @@ -66,6 +66,7 @@ static inline void file_free(struct file *f)
> > if (likely(!(f->f_mode & FMODE_NOACCOUNT)))
> > percpu_counter_dec(&nr_files);
> > put_cred(f->f_cred);
> > + put_cred(f->f_owner.cred);
>
> if (likely(f->f_cred == f->f_owner.cred)) {
> put_cred_many(f->f_cred, 2);
> } else {
> put_cred(f->f_cred);
> put_cred(f->f_owner.cred);
> }
>
> > if (unlikely(f->f_mode & FMODE_BACKING)) {
> > path_put(backing_file_user_path(f));
> > kfree(backing_file(f));
> > @@ -149,9 +150,11 @@ static int init_file(struct file *f, int flags, const struct cred *cred)
> > int error;
> >
> > f->f_cred = get_cred(cred);
> > + f->f_owner.cred = get_cred(cred);
>
> f->f_cred = f->f_owner.cred = get_cred_many(cred, 2);
>
> > error = security_file_alloc(f);
> > if (unlikely(error)) {
> > put_cred(f->f_cred);
> > + put_cred(f->f_owner.cred);
>
> put_cred_many(cred, 2);
>
> > return error;
> > }
>
next prev parent reply other threads:[~2024-08-13 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 17:44 [PATCH v2] fs,security: Fix file_set_fowner LSM hook inconsistencies Mickaël Salaün
2024-08-12 21:45 ` Mateusz Guzik
2024-08-13 10:09 ` Mickaël Salaün [this message]
2024-08-12 22:26 ` Paul Moore
2024-08-13 10:05 ` Mickaël Salaün
2024-08-13 15:04 ` Paul Moore
2024-08-13 18:28 ` Mickaël Salaün
2024-08-13 23:39 ` Paul Moore
2024-08-14 7:44 ` Mateusz Guzik
2024-08-14 12:35 ` Mickaël Salaün
2024-08-14 15:13 ` Paul Moore
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=20240813.iidaejohj5Oo@digikod.net \
--to=mic@digikod.net \
--cc=brauner@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=fahimitahera@gmail.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=stephen.smalley.work@gmail.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