On Mon, Aug 15, 2022 at 10:03:21PM +0800, Jiacheng Xu wrote: > Patch: > Fix this bug by moving the assignment of inode->i_private before > security_inode_alloc. > An ad-hoc patch is proposed: > https://patchwork.kernel.org/project/linux-fsdevel/patch/20211011030956.2459172-1-mudongliangabcd@xxxxxxxxx/ ... and that looks like utter bollocks. Why does security_inode_alloc() look at ->i_private? Which LSM is involved?
