All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <YvqPN2T3Q8pfnCoV@ZenIV>

diff --git a/a/1.txt b/N1/1.txt
index a2342b1..eca30d4 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -5,7 +5,7 @@ On Mon, Aug 15, 2022 at 07:02:14PM +0100, Al Viro 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 8345988..95c3fff 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,14 +1,14 @@
  "ref\0CAO4S-mficMz1mQW06EuCF+o11+mRDiCpufqVfoHkcRbQbs8kVw@mail.gmail.com\0"
  "ref\0YvqKJppIL4lVCn9+@ZenIV\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:23:51 +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 07:02:14PM +0100, Al Viro wrote:\n"
@@ -18,7 +18,7 @@
  "> > 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?\n"
@@ -46,4 +46,4 @@
  "just a theoretical problem - nilfs2 has actually stepped into that\n"
  "[reference to report]\""
 
-e7d80f6f27ae49ff4089136a6a9a69925bfcc277f5921ca31505227b40ac81f2
+7374667a71a655eb0d39ab0227ddba78065847f59cd9dbf4ee0218f05c5b2cbe

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.