diff for duplicates of <20181120183926.GA124387@google.com> diff --git a/a/1.txt b/N1/1.txt index 3c64672..4b9913b 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,16 +1,16 @@ 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 cd4bd5d..d6a898d 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,37 +1,23 @@ "ref\020181120052137.74317-1-joel@joelfernandes.org\0" "ref\0CALCETrXgBENat=5=7EuU-ttQ-YSXT+ifjLGc=hpJ=unRgSsndw@mail.gmail.com\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 10:39:26 -0800\0" - "To\0Andy Lutomirski <luto@kernel.org>\0" - "Cc\0LKML <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> - " Stephen Rothwell <sfr@canb.auug.org.au>\0" "\00:1\0" "b\0" "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" @@ -42,4 +28,4 @@ "\n" - Joel -280ed8a0d7f5fc87075f6614fe7c95a2d0e4decc06e0c1cbe5da39bfc9af6694 +acce7f6ba8523d5e8642cdceba78994a2fd72649b3711c5775b6d49df3156b41
diff --git a/a/1.txt b/N2/1.txt index 3c64672..9f7ad6e 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,4 +1,4 @@ -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: > > @@ -7,10 +7,10 @@ On Tue, Nov 20, 2018 at 07:13:17AM -0800, Andy Lutomirski wrote: > > 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 cd4bd5d..9dbf8be 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,25 +1,11 @@ "ref\020181120052137.74317-1-joel@joelfernandes.org\0" "ref\0CALCETrXgBENat=5=7EuU-ttQ-YSXT+ifjLGc=hpJ=unRgSsndw@mail.gmail.com\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 10:39:26 -0800\0" - "To\0Andy Lutomirski <luto@kernel.org>\0" - "Cc\0LKML <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> - " Stephen Rothwell <sfr@canb.auug.org.au>\0" "\00:1\0" "b\0" - "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" "> >\n" @@ -28,10 +14,10 @@ "> > 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" @@ -42,4 +28,4 @@ "\n" - Joel -280ed8a0d7f5fc87075f6614fe7c95a2d0e4decc06e0c1cbe5da39bfc9af6694 +f8d72ecf7e97868c7820072305965ac4919560d88ceedb7e7f488c8c18b6ee39
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.