All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <CAKFNMokX6wudO+WJbdc4-1gTXLXn59=dvm0CLGeXAFiA+kJXdg@mail.gmail.com>

diff --git a/a/1.txt b/N1/1.txt
index 32bff76..43c3637 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -61,9 +61,9 @@ On Tue, Nov 8, 2022 at 9:24 PM Ryusuke Konishi wrote:
 > > >>>> nilfs_sufile_header's sh_last_alloc is not updated. In such case, we will
 > > >>>> add a bh in two segbuf->sb_segsum_buffers. And finally cause list error.
 > > >>>>
-> > >>>> Reported-by: syzbot+77e4f005cb899d4268d1@syzkaller.appspotmail.com
+> > >>>> Reported-by: syzbot+77e4f005cb899d4268d1-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org
 > > >>>> Fixes: 9ff05123e3bf ("nilfs2: segment constructor")
-> > >>>> Signed-off-by: Liu Shixin <liushixin2@huawei.com>
+> > >>>> Signed-off-by: Liu Shixin <liushixin2-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
 > > >>>> ---
 > > >>>>  fs/nilfs2/segment.c | 1 +
 > > >>>>  fs/nilfs2/sufile.c  | 2 +-
@@ -137,7 +137,7 @@ On Tue, Nov 8, 2022 at 9:24 PM Ryusuke Konishi wrote:
 > > >>> Since segments are used cyclically, wouldn't comparison with the max
 > > >>> function break down there?
 > > >>> (I mean it seems that sh_last_alloc may be chosen unintentionally at the end.)
-> > >> Thanks for the heads-up,I need to look at it again. This patch can only prevent this problem,
+> > >> Thanks for the heads-up,I need to look at it again. This patch can only prevent this problem,
 > > >> and seems to need improvement. Maybe there is a more reasonable solution.
 > > >>
 > > >> Thanks,
diff --git a/a/content_digest b/N1/content_digest
index 63fbd7e..a9968f7 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -17,7 +17,10 @@
   "ref\0CAKFNMomK=C4JY7ftNQs7Zs3dr0m=e_k-vVXTfmR-mpumuGUtDw\@mail.gmail.com\0"
 ]
 [
-  "From\0Ryusuke Konishi <konishi.ryusuke\@gmail.com>\0"
+  "ref\0CAKFNMomK=C4JY7ftNQs7Zs3dr0m=e_k-vVXTfmR-mpumuGUtDw-JsoAwUIsXosN+BqQ9rBEUg\@public.gmane.org\0"
+]
+[
+  "From\0Ryusuke Konishi <konishi.ryusuke-Re5JQEeQqe8AvxtiuMwx3w\@public.gmane.org>\0"
 ]
 [
   "Subject\0Re: [PATCH] nilfs2: fix NULL pointer dereference in nilfs_segctor_prepare_write()\0"
@@ -26,12 +29,12 @@
   "Date\0Wed, 9 Nov 2022 00:13:24 +0900\0"
 ]
 [
-  "To\0Liu Shixin <liushixin2\@huawei.com>\0"
+  "To\0Liu Shixin <liushixin2-hv44wF8Li93QT0dZR+AlfA\@public.gmane.org>\0"
 ]
 [
-  "Cc\0Andrew Morton <akpm\@linux-foundation.org>",
-  " linux-nilfs\@vger.kernel.org",
-  " linux-kernel\@vger.kernel.org\0"
+  "Cc\0Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b\@public.gmane.org>",
+  " linux-nilfs-u79uwXL29TY76Z2rM5mHXA\@public.gmane.org",
+  " linux-kernel-u79uwXL29TY76Z2rM5mHXA\@public.gmane.org\0"
 ]
 [
   "\0000:1\0"
@@ -103,9 +106,9 @@
   "> > >>>> nilfs_sufile_header's sh_last_alloc is not updated. In such case, we will\n",
   "> > >>>> add a bh in two segbuf->sb_segsum_buffers. And finally cause list error.\n",
   "> > >>>>\n",
-  "> > >>>> Reported-by: syzbot+77e4f005cb899d4268d1\@syzkaller.appspotmail.com\n",
+  "> > >>>> Reported-by: syzbot+77e4f005cb899d4268d1-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8\@public.gmane.org\n",
   "> > >>>> Fixes: 9ff05123e3bf (\"nilfs2: segment constructor\")\n",
-  "> > >>>> Signed-off-by: Liu Shixin <liushixin2\@huawei.com>\n",
+  "> > >>>> Signed-off-by: Liu Shixin <liushixin2-hv44wF8Li93QT0dZR+AlfA\@public.gmane.org>\n",
   "> > >>>> ---\n",
   "> > >>>>  fs/nilfs2/segment.c | 1 +\n",
   "> > >>>>  fs/nilfs2/sufile.c  | 2 +-\n",
@@ -179,7 +182,7 @@
   "> > >>> Since segments are used cyclically, wouldn't comparison with the max\n",
   "> > >>> function break down there?\n",
   "> > >>> (I mean it seems that sh_last_alloc may be chosen unintentionally at the end.)\n",
-  "> > >> Thanks for the heads-up\357\274\214I need to look at it again. This patch can only prevent this problem,\n",
+  "> > >> Thanks for the heads-up\303\257\302\274\305\222I need to look at it again. This patch can only prevent this problem,\n",
   "> > >> and seems to need improvement. Maybe there is a more reasonable solution.\n",
   "> > >>\n",
   "> > >> Thanks,\n",
@@ -329,4 +332,4 @@
   "Ryusuke Konishi"
 ]
 
-d18e9fa8dfcaa4fdec120c4d167b380f228b970bfd9c8b1bebb3c1335058ea73
+913c8deb787e1118c1aa4c85b0d97a5c7d38e43398876ff97f878dd3dafa41c0

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.