diff for duplicates of <YvqKJppIL4lVCn9+@ZenIV> diff --git a/a/1.txt b/N1/1.txt index 4c8a3ea..b5e5199 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -4,7 +4,7 @@ On Mon, Aug 15, 2022 at 10:03:21PM +0800, Jiacheng Xu wrote: > 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org/ +> https://patchwork.kernel.org/project/linux-fsdevel/patch/20211011030956.2459172-1-mudongliangabcd@gmail.com/ ... and that looks like utter bollocks. Why does security_inode_alloc() look at ->i_private? Which LSM is involved? diff --git a/a/content_digest b/N1/content_digest index 6cff367..4b51a32 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,14 +1,13 @@ "ref\0CAO4S-mficMz1mQW06EuCF+o11+mRDiCpufqVfoHkcRbQbs8kVw@mail.gmail.com\0" - "ref\0CAO4S-mficMz1mQW06EuCF+o11+mRDiCpufqVfoHkcRbQbs8kVw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org\0" - "From\0Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>\0" + "From\0Al Viro <viro@zeniv.linux.org.uk>\0" "Subject\0Re: KASAN: use-after-free in nilfs_mdt_destroy\0" "Date\0Mon, 15 Aug 2022 19:02:14 +0100\0" - "To\0Jiacheng Xu <578001344xu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\0" - "Cc\0linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" - gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org - konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org - linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org - " security-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org\0" + "To\0Jiacheng Xu <578001344xu@gmail.com>\0" + "Cc\0linux-kernel@vger.kernel.org" + gregkh@linuxfoundation.org + konishi.ryusuke@gmail.com + linux-nilfs@vger.kernel.org + " security@kernel.org\0" "\00:1\0" "b\0" "On Mon, Aug 15, 2022 at 10:03:21PM +0800, Jiacheng Xu wrote:\n" @@ -17,9 +16,9 @@ "> Fix this bug by moving the assignment of inode->i_private before\n" "> security_inode_alloc.\n" "> An ad-hoc patch is proposed:\n" - "> https://patchwork.kernel.org/project/linux-fsdevel/patch/20211011030956.2459172-1-mudongliangabcd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org/\n" + "> https://patchwork.kernel.org/project/linux-fsdevel/patch/20211011030956.2459172-1-mudongliangabcd@gmail.com/\n" "\n" "... and that looks like utter bollocks. Why does security_inode_alloc()\n" look at ->i_private? Which LSM is involved? -288cc75acfb5f859b7e7e26d4362e823642e44d1a5af988c7697edddd963f476 +87e6e0d9928e5eb2be65de4311722f3e2e2c6f5531c22cea43de4b403f803ac2
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.