[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240709-bauaufsicht-bildschirm-331fb59cb6fb@brauner>
Date: Tue, 9 Jul 2024 07:46:53 +0200
From: Christian Brauner <brauner@...nel.org>
To: Mickaël Salaün <mic@...ikod.net>
Cc: Paul Moore <paul@...l-moore.com>, 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
> > ... 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.
Powered by blists - more mailing lists