diff for duplicates of <20181120204710.GB22801@google.com> diff --git a/a/1.txt b/N1/1.txt index c2b2195..ef98e70 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,24 +1,24 @@ 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 39d3b24..196eab5 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,47 +3,32 @@ "ref\020181120183926.GA124387@google.com\0" "ref\020181121070658.011d576d@canb.auug.org.au\0" "ref\0469B80CB-D982-4802-A81D-95AC493D7E87@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 12:47:10 -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 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" @@ -66,4 +51,4 @@ "\n" - Joel -d2512a7ad5b240c69cb412e21ce7fbc9cac148ad1892f4ff4b978f7019de851c +f3aa60f0bd753e887b1d2702e13a75afebc90ac02399509315a7981eabef1bc4
diff --git a/a/1.txt b/N2/1.txt index c2b2195..80ef295 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,24 +1,24 @@ -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 39d3b24..39bdc4a 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -3,47 +3,32 @@ "ref\020181120183926.GA124387@google.com\0" "ref\020181121070658.011d576d@canb.auug.org.au\0" "ref\0469B80CB-D982-4802-A81D-95AC493D7E87@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 12:47:10 -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 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" @@ -66,4 +51,4 @@ "\n" - Joel -d2512a7ad5b240c69cb412e21ce7fbc9cac148ad1892f4ff4b978f7019de851c +c7ca78075dd69e81810e6880c4c83a42c3cbd013623b3d4aefa962b6ad8c4066
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.