diff for duplicates of <20181110032005.GA22238@google.com> diff --git a/a/1.txt b/N1/1.txt index 454b8b4..f36ea9e 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,7 +1,7 @@ On Fri, Nov 09, 2018 at 10:19:03PM +0100, Jann Horn wrote: -> On Fri, Nov 9, 2018 at 10:06 PM Jann Horn <jannh@google.com> wrote: +> On Fri, Nov 9, 2018 at 10:06 PM Jann Horn <jannh at google.com> wrote: > > On Fri, Nov 9, 2018 at 9:46 PM Joel Fernandes (Google) -> > <joel@joelfernandes.org> wrote: +> > <joel at joelfernandes.org> wrote: > > > Android uses ashmem for sharing memory regions. We are looking forward > > > to migrating all usecases of ashmem to memfd so that we can possibly > > > remove the ashmem driver in the future from staging while also @@ -28,13 +28,13 @@ On Fri, Nov 09, 2018 at 10:19:03PM +0100, Jann Horn wrote: > > > The following program shows the seal > > > working in action: > > [...] -> > > Cc: jreck@google.com -> > > Cc: john.stultz@linaro.org -> > > Cc: tkjos@google.com -> > > Cc: gregkh@linuxfoundation.org -> > > Cc: hch@infradead.org -> > > Reviewed-by: John Stultz <john.stultz@linaro.org> -> > > Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org> +> > > Cc: jreck at google.com +> > > Cc: john.stultz at linaro.org +> > > Cc: tkjos at google.com +> > > Cc: gregkh at linuxfoundation.org +> > > Cc: hch at infradead.org +> > > Reviewed-by: John Stultz <john.stultz at linaro.org> +> > > Signed-off-by: Joel Fernandes (Google) <joel at joelfernandes.org> > > > --- > > [...] > > > diff --git a/mm/memfd.c b/mm/memfd.c @@ -108,7 +108,7 @@ solution and it works. Do you mind testing it and I'll add your and Tested-by to the new fix? The patch is based on top of this series. ---8<----------- -From: "Joel Fernandes (Google)" <joel@joelfernandes.org> +From: "Joel Fernandes (Google)" <joel at joelfernandes.org> Subject: [PATCH] mm/memfd: Fix possible promotion to writeable of sealed memfd Jann Horn found that reopening an F_SEAL_FUTURE_WRITE sealed memfd @@ -116,8 +116,8 @@ through /proc/self/fd/N symlink as writeable succeeds. The simplest fix without causing ABI breakages and ugly VFS hacks is to simply deny all opens on F_SEAL_FUTURE_WRITE sealed fds. -Reported-by: Jann Horn <jannh@google.com> -Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org> +Reported-by: Jann Horn <jannh at google.com> +Signed-off-by: Joel Fernandes (Google) <joel at joelfernandes.org> --- mm/shmem.c | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/a/content_digest b/N1/content_digest index 8c1c235..f2e5c88 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,39 +1,15 @@ "ref\020181108041537.39694-1-joel@joelfernandes.org\0" "ref\0CAG48ez1h=v-JYnDw81HaYJzOfrNhwYksxmc2r=cJvdQVgYM+NA@mail.gmail.com\0" "ref\0CAG48ez0kQ4d566bXTFOYANDgii-stL-Qj-oyaBzvfxdV=PU-7g@mail.gmail.com\0" - "From\0Joel Fernandes <joel@joelfernandes.org>\0" - "Subject\0Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd\0" + "From\0joel at joelfernandes.org (Joel Fernandes)\0" + "Subject\0[PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd\0" "Date\0Fri, 9 Nov 2018 19:20:05 -0800\0" - "To\0Jann Horn <jannh@google.com>\0" - "Cc\0kernel list <linux-kernel@vger.kernel.org>" - jreck@google.com - John Stultz <john.stultz@linaro.org> - Todd Kjos <tkjos@google.com> - Greg Kroah-Hartman <gregkh@linuxfoundation.org> - Christoph Hellwig <hch@infradead.org> - Al Viro <viro@zeniv.linux.org.uk> - Andrew Morton <akpm@linux-foundation.org> - Daniel Colascione <dancol@google.com> - Bruce Fields <bfields@fieldses.org> - jlayton@kernel.org - Khalid Aziz <khalid.aziz@oracle.com> - Lei.Yang@windriver.com - linux-fsdevel@vger.kernel.org - linux-kselftest@vger.kernel.org - Linux-MM <linux-mm@kvack.org> - marcandre.lureau@redhat.com - Mike Kravetz <mike.kravetz@oracle.com> - minchan@kernel.org - shuah@kernel.org - valdis.kletnieks@vt.edu - Hugh Dickins <hughd@google.com> - " Linux API <linux-api@vger.kernel.org>\0" "\00:1\0" "b\0" "On Fri, Nov 09, 2018 at 10:19:03PM +0100, Jann Horn wrote:\n" - "> On Fri, Nov 9, 2018 at 10:06 PM Jann Horn <jannh@google.com> wrote:\n" + "> On Fri, Nov 9, 2018 at 10:06 PM Jann Horn <jannh at google.com> wrote:\n" "> > On Fri, Nov 9, 2018 at 9:46 PM Joel Fernandes (Google)\n" - "> > <joel@joelfernandes.org> wrote:\n" + "> > <joel at joelfernandes.org> wrote:\n" "> > > Android uses ashmem for sharing memory regions. We are looking forward\n" "> > > to migrating all usecases of ashmem to memfd so that we can possibly\n" "> > > remove the ashmem driver in the future from staging while also\n" @@ -60,13 +36,13 @@ "> > > The following program shows the seal\n" "> > > working in action:\n" "> > [...]\n" - "> > > Cc: jreck@google.com\n" - "> > > Cc: john.stultz@linaro.org\n" - "> > > Cc: tkjos@google.com\n" - "> > > Cc: gregkh@linuxfoundation.org\n" - "> > > Cc: hch@infradead.org\n" - "> > > Reviewed-by: John Stultz <john.stultz@linaro.org>\n" - "> > > Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>\n" + "> > > Cc: jreck at google.com\n" + "> > > Cc: john.stultz at linaro.org\n" + "> > > Cc: tkjos at google.com\n" + "> > > Cc: gregkh at linuxfoundation.org\n" + "> > > Cc: hch at infradead.org\n" + "> > > Reviewed-by: John Stultz <john.stultz at linaro.org>\n" + "> > > Signed-off-by: Joel Fernandes (Google) <joel at joelfernandes.org>\n" "> > > ---\n" "> > [...]\n" "> > > diff --git a/mm/memfd.c b/mm/memfd.c\n" @@ -140,7 +116,7 @@ "to the new fix? The patch is based on top of this series.\n" "\n" "---8<-----------\n" - "From: \"Joel Fernandes (Google)\" <joel@joelfernandes.org>\n" + "From: \"Joel Fernandes (Google)\" <joel at joelfernandes.org>\n" "Subject: [PATCH] mm/memfd: Fix possible promotion to writeable of sealed memfd\n" "\n" "Jann Horn found that reopening an F_SEAL_FUTURE_WRITE sealed memfd\n" @@ -148,8 +124,8 @@ "without causing ABI breakages and ugly VFS hacks is to simply deny all\n" "opens on F_SEAL_FUTURE_WRITE sealed fds.\n" "\n" - "Reported-by: Jann Horn <jannh@google.com>\n" - "Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>\n" + "Reported-by: Jann Horn <jannh at google.com>\n" + "Signed-off-by: Joel Fernandes (Google) <joel at joelfernandes.org>\n" "---\n" " mm/shmem.c | 18 ++++++++++++++++++\n" " 1 file changed, 18 insertions(+)\n" @@ -187,4 +163,4 @@ "-- \n" 2.19.1.930.g4563a0d9d0-goog -0147ebd89f9956ed86c20e52547b4dd2af38828cf723b5d643e7fe85f6f89473 +e5298458b4ec0a6b4bf2c0e72f907308041430efe4399df5bb2f5f288839eeeb
diff --git a/a/1.txt b/N2/1.txt index 454b8b4..1912631 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,5 +1,5 @@ -On Fri, Nov 09, 2018 at 10:19:03PM +0100, Jann Horn wrote: -> On Fri, Nov 9, 2018 at 10:06 PM Jann Horn <jannh@google.com> wrote: +On Fri, Nov 09, 2018@10:19:03PM +0100, Jann Horn wrote: +> On Fri, Nov 9, 2018@10:06 PM Jann Horn <jannh@google.com> wrote: > > On Fri, Nov 9, 2018 at 9:46 PM Joel Fernandes (Google) > > <joel@joelfernandes.org> wrote: > > > Android uses ashmem for sharing memory regions. We are looking forward @@ -28,13 +28,13 @@ On Fri, Nov 09, 2018 at 10:19:03PM +0100, Jann Horn wrote: > > > The following program shows the seal > > > working in action: > > [...] -> > > Cc: jreck@google.com -> > > Cc: john.stultz@linaro.org -> > > Cc: tkjos@google.com -> > > Cc: gregkh@linuxfoundation.org -> > > Cc: hch@infradead.org -> > > Reviewed-by: John Stultz <john.stultz@linaro.org> -> > > Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org> +> > > Cc: jreck at google.com +> > > Cc: john.stultz at linaro.org +> > > Cc: tkjos at google.com +> > > Cc: gregkh at linuxfoundation.org +> > > Cc: hch at infradead.org +> > > Reviewed-by: John Stultz <john.stultz at linaro.org> +> > > Signed-off-by: Joel Fernandes (Google) <joel at joelfernandes.org> > > > --- > > [...] > > > diff --git a/mm/memfd.c b/mm/memfd.c @@ -116,8 +116,8 @@ through /proc/self/fd/N symlink as writeable succeeds. The simplest fix without causing ABI breakages and ugly VFS hacks is to simply deny all opens on F_SEAL_FUTURE_WRITE sealed fds. -Reported-by: Jann Horn <jannh@google.com> -Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org> +Reported-by: Jann Horn <jannh at google.com> +Signed-off-by: Joel Fernandes (Google) <joel at joelfernandes.org> --- mm/shmem.c | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/a/content_digest b/N2/content_digest index 8c1c235..c616f2b 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,37 +1,13 @@ "ref\020181108041537.39694-1-joel@joelfernandes.org\0" "ref\0CAG48ez1h=v-JYnDw81HaYJzOfrNhwYksxmc2r=cJvdQVgYM+NA@mail.gmail.com\0" "ref\0CAG48ez0kQ4d566bXTFOYANDgii-stL-Qj-oyaBzvfxdV=PU-7g@mail.gmail.com\0" - "From\0Joel Fernandes <joel@joelfernandes.org>\0" - "Subject\0Re: [PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd\0" + "From\0joel@joelfernandes.org (Joel Fernandes)\0" + "Subject\0[PATCH v3 resend 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd\0" "Date\0Fri, 9 Nov 2018 19:20:05 -0800\0" - "To\0Jann Horn <jannh@google.com>\0" - "Cc\0kernel list <linux-kernel@vger.kernel.org>" - jreck@google.com - John Stultz <john.stultz@linaro.org> - Todd Kjos <tkjos@google.com> - Greg Kroah-Hartman <gregkh@linuxfoundation.org> - Christoph Hellwig <hch@infradead.org> - Al Viro <viro@zeniv.linux.org.uk> - Andrew Morton <akpm@linux-foundation.org> - Daniel Colascione <dancol@google.com> - Bruce Fields <bfields@fieldses.org> - jlayton@kernel.org - Khalid Aziz <khalid.aziz@oracle.com> - Lei.Yang@windriver.com - linux-fsdevel@vger.kernel.org - linux-kselftest@vger.kernel.org - Linux-MM <linux-mm@kvack.org> - marcandre.lureau@redhat.com - Mike Kravetz <mike.kravetz@oracle.com> - minchan@kernel.org - shuah@kernel.org - valdis.kletnieks@vt.edu - Hugh Dickins <hughd@google.com> - " Linux API <linux-api@vger.kernel.org>\0" "\00:1\0" "b\0" - "On Fri, Nov 09, 2018 at 10:19:03PM +0100, Jann Horn wrote:\n" - "> On Fri, Nov 9, 2018 at 10:06 PM Jann Horn <jannh@google.com> wrote:\n" + "On Fri, Nov 09, 2018@10:19:03PM +0100, Jann Horn wrote:\n" + "> On Fri, Nov 9, 2018@10:06 PM Jann Horn <jannh@google.com> wrote:\n" "> > On Fri, Nov 9, 2018 at 9:46 PM Joel Fernandes (Google)\n" "> > <joel@joelfernandes.org> wrote:\n" "> > > Android uses ashmem for sharing memory regions. We are looking forward\n" @@ -60,13 +36,13 @@ "> > > The following program shows the seal\n" "> > > working in action:\n" "> > [...]\n" - "> > > Cc: jreck@google.com\n" - "> > > Cc: john.stultz@linaro.org\n" - "> > > Cc: tkjos@google.com\n" - "> > > Cc: gregkh@linuxfoundation.org\n" - "> > > Cc: hch@infradead.org\n" - "> > > Reviewed-by: John Stultz <john.stultz@linaro.org>\n" - "> > > Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>\n" + "> > > Cc: jreck at google.com\n" + "> > > Cc: john.stultz at linaro.org\n" + "> > > Cc: tkjos at google.com\n" + "> > > Cc: gregkh at linuxfoundation.org\n" + "> > > Cc: hch at infradead.org\n" + "> > > Reviewed-by: John Stultz <john.stultz at linaro.org>\n" + "> > > Signed-off-by: Joel Fernandes (Google) <joel at joelfernandes.org>\n" "> > > ---\n" "> > [...]\n" "> > > diff --git a/mm/memfd.c b/mm/memfd.c\n" @@ -148,8 +124,8 @@ "without causing ABI breakages and ugly VFS hacks is to simply deny all\n" "opens on F_SEAL_FUTURE_WRITE sealed fds.\n" "\n" - "Reported-by: Jann Horn <jannh@google.com>\n" - "Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>\n" + "Reported-by: Jann Horn <jannh at google.com>\n" + "Signed-off-by: Joel Fernandes (Google) <joel at joelfernandes.org>\n" "---\n" " mm/shmem.c | 18 ++++++++++++++++++\n" " 1 file changed, 18 insertions(+)\n" @@ -187,4 +163,4 @@ "-- \n" 2.19.1.930.g4563a0d9d0-goog -0147ebd89f9956ed86c20e52547b4dd2af38828cf723b5d643e7fe85f6f89473 +623bdc04e434839d8f2c536dcc321e1d3ea1973437b5ccbec6143cad13e5b946
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.