diff for duplicates of <20181120211335.GC22801@google.com> diff --git a/a/1.txt b/N1/1.txt index dee428b..bfd1815 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,28 +1,28 @@ On Tue, Nov 20, 2018 at 02:02:49PM -0700, Andy Lutomirski wrote: > -> > On Nov 20, 2018, at 1:47 PM, Joel Fernandes <joel@joelfernandes.org> wrote: +> > On Nov 20, 2018, at 1:47 PM, Joel Fernandes <joel at joelfernandes.org> wrote: > > > >> On Tue, Nov 20, 2018 at 01:33:18PM -0700, Andy Lutomirski wrote: > >> -> >>> On Nov 20, 2018, at 1:07 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote: +> >>> On Nov 20, 2018, at 1:07 PM, Stephen Rothwell <sfr at canb.auug.org.au> wrote: > >>> > >>> Hi Joel, > >>> -> >>>>> On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes <joel@joelfernandes.org> wrote: +> >>>>> On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes <joel at joelfernandes.org> wrote: > >>>>> > >>>>> On Tue, Nov 20, 2018 at 07:13:17AM -0800, Andy Lutomirski wrote: > >>>>> On Mon, Nov 19, 2018 at 9:21 PM Joel Fernandes (Google) -> >>>>> <joel@joelfernandes.org> wrote: +> >>>>> <joel at joelfernandes.org> wrote: > >>>>>> > >>>>>> A better way to do F_SEAL_FUTURE_WRITE seal was discussed [1] last week > >>>>>> where we don't need to modify core VFS structures to get the same > >>>>>> behavior of the seal. This solves several side-effects pointed out by > >>>>>> Andy [2]. > >>>>>> -> >>>>>> [1] https://lore.kernel.org/lkml/20181111173650.GA256781@google.com/ -> >>>>>> [2] https://lore.kernel.org/lkml/69CE06CC-E47C-4992-848A-66EB23EE6C74@amacapital.net/ +> >>>>>> [1] https://lore.kernel.org/lkml/20181111173650.GA256781 at google.com/ +> >>>>>> [2] https://lore.kernel.org/lkml/69CE06CC-E47C-4992-848A-66EB23EE6C74 at amacapital.net/ > >>>>>> -> >>>>>> Suggested-by: Andy Lutomirski <luto@kernel.org> +> >>>>>> Suggested-by: Andy Lutomirski <luto at kernel.org> > >>>>>> Fixes: 5e653c2923fd ("mm: Add an F_SEAL_FUTURE_WRITE seal to memfd") > >>>>> > >>>>> What tree is that commit in? Can we not just fold this in? diff --git a/a/content_digest b/N1/content_digest index 636b553..9d24ca2 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,51 +5,36 @@ "ref\0469B80CB-D982-4802-A81D-95AC493D7E87@amacapital.net\0" "ref\020181120204710.GB22801@google.com\0" "ref\0F8E28229-C99E-4711-982B-5B5DE0F70F16@amacapital.net\0" - "From\0Joel Fernandes <joel@joelfernandes.org>\0" - "Subject\0Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust\0" + "From\0joel at joelfernandes.org (Joel Fernandes)\0" + "Subject\0[PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust\0" "Date\0Tue, 20 Nov 2018 13:13:35 -0800\0" - "To\0Andy Lutomirski <luto@amacapital.net>\0" - "Cc\0Stephen Rothwell <sfr@canb.auug.org.au>" - Andy Lutomirski <luto@kernel.org> - LKML <linux-kernel@vger.kernel.org> - Andrew Morton <akpm@linux-foundation.org> - Hugh Dickins <hughd@google.com> - Jann Horn <jannh@google.com> - Khalid Aziz <khalid.aziz@oracle.com> - Linux API <linux-api@vger.kernel.org> - open list:KERNEL SELFTEST FRAMEWORK <linux-kselftest@vger.kernel.org> - Linux-MM <linux-mm@kvack.org> - marcandre.lureau@redhat.com - Matthew Wilcox <willy@infradead.org> - Mike Kravetz <mike.kravetz@oracle.com> - " Shuah Khan <shuah@kernel.org>\0" "\00:1\0" "b\0" "On Tue, Nov 20, 2018 at 02:02:49PM -0700, Andy Lutomirski wrote:\n" "> \n" - "> > On Nov 20, 2018, at 1:47 PM, Joel Fernandes <joel@joelfernandes.org> wrote:\n" + "> > On Nov 20, 2018, at 1:47 PM, Joel Fernandes <joel at joelfernandes.org> wrote:\n" "> > \n" "> >> On Tue, Nov 20, 2018 at 01:33:18PM -0700, Andy Lutomirski wrote:\n" "> >> \n" - "> >>> On Nov 20, 2018, at 1:07 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:\n" + "> >>> On Nov 20, 2018, at 1:07 PM, Stephen Rothwell <sfr at canb.auug.org.au> wrote:\n" "> >>> \n" "> >>> Hi Joel,\n" "> >>> \n" - "> >>>>> On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes <joel@joelfernandes.org> wrote:\n" + "> >>>>> On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes <joel at joelfernandes.org> wrote:\n" "> >>>>> \n" "> >>>>> On Tue, Nov 20, 2018 at 07:13:17AM -0800, Andy Lutomirski wrote:\n" "> >>>>> On Mon, Nov 19, 2018 at 9:21 PM Joel Fernandes (Google)\n" - "> >>>>> <joel@joelfernandes.org> wrote: \n" + "> >>>>> <joel at joelfernandes.org> wrote: \n" "> >>>>>> \n" "> >>>>>> A better way to do F_SEAL_FUTURE_WRITE seal was discussed [1] last week\n" "> >>>>>> where we don't need to modify core VFS structures to get the same\n" "> >>>>>> behavior of the seal. This solves several side-effects pointed out by\n" "> >>>>>> Andy [2].\n" "> >>>>>> \n" - "> >>>>>> [1] https://lore.kernel.org/lkml/20181111173650.GA256781@google.com/\n" - "> >>>>>> [2] https://lore.kernel.org/lkml/69CE06CC-E47C-4992-848A-66EB23EE6C74@amacapital.net/\n" + "> >>>>>> [1] https://lore.kernel.org/lkml/20181111173650.GA256781 at google.com/\n" + "> >>>>>> [2] https://lore.kernel.org/lkml/69CE06CC-E47C-4992-848A-66EB23EE6C74 at amacapital.net/\n" "> >>>>>> \n" - "> >>>>>> Suggested-by: Andy Lutomirski <luto@kernel.org>\n" + "> >>>>>> Suggested-by: Andy Lutomirski <luto at kernel.org>\n" "> >>>>>> Fixes: 5e653c2923fd (\"mm: Add an F_SEAL_FUTURE_WRITE seal to memfd\") \n" "> >>>>> \n" "> >>>>> What tree is that commit in? Can we not just fold this in? \n" @@ -90,4 +75,4 @@ "\n" - Joel -1efe53d46176ac9ff9d89e229f05fc1da4459c31aa2888840849454ab57beb6f +442641a5b22abd194df7319d004ebfec24603d05a3d4a22b9cfb5da734d75d87
diff --git a/a/1.txt b/N2/1.txt index dee428b..4ca0060 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,28 +1,28 @@ -On Tue, Nov 20, 2018 at 02:02:49PM -0700, Andy Lutomirski wrote: +On Tue, Nov 20, 2018@02:02:49PM -0700, Andy Lutomirski wrote: > -> > On Nov 20, 2018, at 1:47 PM, Joel Fernandes <joel@joelfernandes.org> wrote: +> > On Nov 20, 2018,@1:47 PM, Joel Fernandes <joel@joelfernandes.org> wrote: > > -> >> On Tue, Nov 20, 2018 at 01:33:18PM -0700, Andy Lutomirski wrote: +> >> On Tue, Nov 20, 2018@01:33:18PM -0700, Andy Lutomirski wrote: > >> -> >>> On Nov 20, 2018, at 1:07 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote: +> >>> On Nov 20, 2018,@1:07 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote: > >>> > >>> Hi Joel, > >>> > >>>>> On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes <joel@joelfernandes.org> wrote: > >>>>> -> >>>>> On Tue, Nov 20, 2018 at 07:13:17AM -0800, Andy Lutomirski wrote: +> >>>>> On Tue, Nov 20, 2018@07:13:17AM -0800, Andy Lutomirski wrote: > >>>>> On Mon, Nov 19, 2018 at 9:21 PM Joel Fernandes (Google) -> >>>>> <joel@joelfernandes.org> wrote: +> >>>>> <joel at joelfernandes.org> wrote: > >>>>>> > >>>>>> A better way to do F_SEAL_FUTURE_WRITE seal was discussed [1] last week > >>>>>> where we don't need to modify core VFS structures to get the same > >>>>>> behavior of the seal. This solves several side-effects pointed out by > >>>>>> Andy [2]. > >>>>>> -> >>>>>> [1] https://lore.kernel.org/lkml/20181111173650.GA256781@google.com/ -> >>>>>> [2] https://lore.kernel.org/lkml/69CE06CC-E47C-4992-848A-66EB23EE6C74@amacapital.net/ +> >>>>>> [1] https://lore.kernel.org/lkml/20181111173650.GA256781 at google.com/ +> >>>>>> [2] https://lore.kernel.org/lkml/69CE06CC-E47C-4992-848A-66EB23EE6C74 at amacapital.net/ > >>>>>> -> >>>>>> Suggested-by: Andy Lutomirski <luto@kernel.org> +> >>>>>> Suggested-by: Andy Lutomirski <luto at kernel.org> > >>>>>> Fixes: 5e653c2923fd ("mm: Add an F_SEAL_FUTURE_WRITE seal to memfd") > >>>>> > >>>>> What tree is that commit in? Can we not just fold this in? diff --git a/a/content_digest b/N2/content_digest index 636b553..f660591 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -5,51 +5,36 @@ "ref\0469B80CB-D982-4802-A81D-95AC493D7E87@amacapital.net\0" "ref\020181120204710.GB22801@google.com\0" "ref\0F8E28229-C99E-4711-982B-5B5DE0F70F16@amacapital.net\0" - "From\0Joel Fernandes <joel@joelfernandes.org>\0" - "Subject\0Re: [PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust\0" + "From\0joel@joelfernandes.org (Joel Fernandes)\0" + "Subject\0[PATCH -next 1/2] mm/memfd: make F_SEAL_FUTURE_WRITE seal more robust\0" "Date\0Tue, 20 Nov 2018 13:13:35 -0800\0" - "To\0Andy Lutomirski <luto@amacapital.net>\0" - "Cc\0Stephen Rothwell <sfr@canb.auug.org.au>" - Andy Lutomirski <luto@kernel.org> - LKML <linux-kernel@vger.kernel.org> - Andrew Morton <akpm@linux-foundation.org> - Hugh Dickins <hughd@google.com> - Jann Horn <jannh@google.com> - Khalid Aziz <khalid.aziz@oracle.com> - Linux API <linux-api@vger.kernel.org> - open list:KERNEL SELFTEST FRAMEWORK <linux-kselftest@vger.kernel.org> - Linux-MM <linux-mm@kvack.org> - marcandre.lureau@redhat.com - Matthew Wilcox <willy@infradead.org> - Mike Kravetz <mike.kravetz@oracle.com> - " Shuah Khan <shuah@kernel.org>\0" "\00:1\0" "b\0" - "On Tue, Nov 20, 2018 at 02:02:49PM -0700, Andy Lutomirski wrote:\n" + "On Tue, Nov 20, 2018@02:02:49PM -0700, Andy Lutomirski wrote:\n" "> \n" - "> > On Nov 20, 2018, at 1:47 PM, Joel Fernandes <joel@joelfernandes.org> wrote:\n" + "> > On Nov 20, 2018,@1:47 PM, Joel Fernandes <joel@joelfernandes.org> wrote:\n" "> > \n" - "> >> On Tue, Nov 20, 2018 at 01:33:18PM -0700, Andy Lutomirski wrote:\n" + "> >> On Tue, Nov 20, 2018@01:33:18PM -0700, Andy Lutomirski wrote:\n" "> >> \n" - "> >>> On Nov 20, 2018, at 1:07 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:\n" + "> >>> On Nov 20, 2018,@1:07 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:\n" "> >>> \n" "> >>> Hi Joel,\n" "> >>> \n" "> >>>>> On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes <joel@joelfernandes.org> wrote:\n" "> >>>>> \n" - "> >>>>> On Tue, Nov 20, 2018 at 07:13:17AM -0800, Andy Lutomirski wrote:\n" + "> >>>>> On Tue, Nov 20, 2018@07:13:17AM -0800, Andy Lutomirski wrote:\n" "> >>>>> On Mon, Nov 19, 2018 at 9:21 PM Joel Fernandes (Google)\n" - "> >>>>> <joel@joelfernandes.org> wrote: \n" + "> >>>>> <joel at joelfernandes.org> wrote: \n" "> >>>>>> \n" "> >>>>>> A better way to do F_SEAL_FUTURE_WRITE seal was discussed [1] last week\n" "> >>>>>> where we don't need to modify core VFS structures to get the same\n" "> >>>>>> behavior of the seal. This solves several side-effects pointed out by\n" "> >>>>>> Andy [2].\n" "> >>>>>> \n" - "> >>>>>> [1] https://lore.kernel.org/lkml/20181111173650.GA256781@google.com/\n" - "> >>>>>> [2] https://lore.kernel.org/lkml/69CE06CC-E47C-4992-848A-66EB23EE6C74@amacapital.net/\n" + "> >>>>>> [1] https://lore.kernel.org/lkml/20181111173650.GA256781 at google.com/\n" + "> >>>>>> [2] https://lore.kernel.org/lkml/69CE06CC-E47C-4992-848A-66EB23EE6C74 at amacapital.net/\n" "> >>>>>> \n" - "> >>>>>> Suggested-by: Andy Lutomirski <luto@kernel.org>\n" + "> >>>>>> Suggested-by: Andy Lutomirski <luto at kernel.org>\n" "> >>>>>> Fixes: 5e653c2923fd (\"mm: Add an F_SEAL_FUTURE_WRITE seal to memfd\") \n" "> >>>>> \n" "> >>>>> What tree is that commit in? Can we not just fold this in? \n" @@ -90,4 +75,4 @@ "\n" - Joel -1efe53d46176ac9ff9d89e229f05fc1da4459c31aa2888840849454ab57beb6f +d5a41fc3552c2a5cc0d4ffd6d188acebc6a095a2aff6622728bdcf7d9a0a719e
diff --git a/a/1.txt b/N3/1.txt index dee428b..8a611c2 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -40,7 +40,7 @@ On Tue, Nov 20, 2018 at 02:02:49PM -0700, Andy Lutomirski wrote: > > I wouldn't go so far to call it nonsense. It was a working patch, it just did > > things differently. Your help with improving the patch is much appreciated. > -> I’m not saying the patch is nonsense — I’m saying the *hash* may be +> Ia??m not saying the patch is nonsense a?? Ia??m saying the *hash* may be > nonsense. akpm uses a bunch of .patch files and all kinds of crazy scripts, > and the mmotm.git tree is not stable at all. > diff --git a/a/content_digest b/N3/content_digest index 636b553..5449ba6 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -67,7 +67,7 @@ "> > I wouldn't go so far to call it nonsense. It was a working patch, it just did\n" "> > things differently. Your help with improving the patch is much appreciated.\n" "> \n" - "> I\342\200\231m not saying the patch is nonsense \342\200\224 I\342\200\231m saying the *hash* may be\n" + "> Ia??m not saying the patch is nonsense a?? Ia??m saying the *hash* may be\n" "> nonsense. akpm uses a bunch of .patch files and all kinds of crazy scripts,\n" "> and the mmotm.git tree is not stable at all.\n" "> \n" @@ -90,4 +90,4 @@ "\n" - Joel -1efe53d46176ac9ff9d89e229f05fc1da4459c31aa2888840849454ab57beb6f +d4cbd24e3a73ec75210e8ac8354375fc5de3634d2be968ae982a1e767536be19
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.