[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhSPAgCCT6CfUbgSEG=zhyXVbHZRsGywi5E_1iScKnUdQA@mail.gmail.com>
Date: Tue, 9 Jul 2024 19:13:35 -0400
From: Paul Moore <paul@...l-moore.com>
To: Mickaël Salaün <mic@...ikod.net>
Cc: Christian Brauner <brauner@...nel.org>, Al Viro <viro@...iv.linux.org.uk>,
Jann Horn <jannh@...gle.com>, "Paul E. McKenney" <paulmck@...nel.org>,
Casey Schaufler <casey@...aufler-ca.com>, Kees Cook <keescook@...omium.org>,
syzbot <syzbot+5446fbf332b0602ede0b@...kaller.appspotmail.com>, jmorris@...ei.org,
linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org,
serge@...lyn.com, syzkaller-bugs@...glegroups.com,
linux-fsdevel@...r.kernel.org
Subject: Re: [syzbot] [lsm?] general protection fault in hook_inode_free_security
On Tue, Jul 9, 2024 at 1:47 AM Christian Brauner <brauner@...nel.org> wrote:
> > > ... or we find a better placement in the VFS for
> > > security_inode_free(), is that is possible. It may not be, our VFS
> > > friends should be able to help here.
>
> The place where you do it currently is pretty good. I don't see an easy
> way to call it from somewhere else without forcing every filesystem to
> either implement a free_inode or destroy_inode hook.
Mickaël, let me play around with some code, if you don't see anything
from me in a day or two, feel free to bug me :)
--
paul-moore.com
Powered by blists - more mailing lists