diff for duplicates of <1494256932.1167.1.camel@gmail.com> diff --git a/a/content_digest b/N1/content_digest index 897f986..ed3d32e 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,47 +2,31 @@ "ref\0CAJcbSZGQsRVg3QZ9QfLn2HBC+RP-7fUTab0bYDJ455d8y8GyNw@mail.gmail.com\0" "ref\020170508073352.caqe3fqf7nuxypgi@gmail.com\0" "ref\020170508075209.7aluvpwildw325rf@gmail.com\0" - "From\0Daniel Micay <danielmicay@gmail.com>\0" + "ref\020170508075209.7aluvpwildw325rf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org\0" + "From\0Daniel Micay <danielmicay-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\0" "Subject\0Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode\0" "Date\0Mon, 08 May 2017 11:22:12 -0400\0" - "To\0Ingo Molnar <mingo@kernel.org>" - " Thomas Garnier <thgarnie@google.com>\0" - "Cc\0Martin Schwidefsky <schwidefsky@de.ibm.com>" - Heiko Carstens <heiko.carstens@de.ibm.com> - Dave Hansen <dave.hansen@intel.com> - Arnd Bergmann <arnd@arndb.de> - Thomas Gleixner <tglx@linutronix.de> - David Howells <dhowells@redhat.com> - " Ren\303\251 Nyffenegger <mail@renenyffenegger.ch>" - Andrew Morton <akpm@linux-foundation.org> - Paul E . McKenney <paulmck@linux.vnet.ibm.com> - Eric W . Biederman <ebiederm@xmission.com> - Oleg Nesterov <oleg@redhat.com> - Pavel Tikhomirov <ptikhomirov@virtuozzo.com> - Ingo Molnar <mingo@redhat.com> - H . Peter Anvin <hpa@zytor.com> - Andy Lutomirski <luto@kernel.org> - Paolo Bonzini <pbonzini@redhat.com> - Rik van Riel <riel@redhat.com> - Kees Cook <keescook@chromium.org> - Josh Poimboeuf <jpoimboe@redhat.com> - Borislav Petkov <bp@alien8.de> - Brian Gerst <brgerst@gmail.com> - Kirill A . Shutemov <kirill.shutemov@linux.intel.com> - Christian Borntraeger <borntraeger@de.ibm.com> - Russell King <linux@armlinux.org.uk> - Will Deacon <will.deacon@arm.com> - Catalin Marinas <catalin.marinas@arm.com> - Mark Rutland <mark.rutland@arm.com> - James Morse <james.morse@arm.com> - linux-s390 <linux-s390@vger.kernel.org> - LKML <linux-kernel@vger.kernel.org> - Linux API <linux-api@vger.kernel.org> - the arch/x86 maintainers <x86@kernel.org> - linux-arm-kernel@lists.infradead.org - Kernel Hardening <kernel-hardening@lists.openwall.com> - Linus Torvalds <torvalds@linux-foundation.org> - " Peter Zijlstra <a.p.zijlstra@chello.nl>\0" + "To\0Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>" + " Thomas Garnier <thgarnie-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>\0" + "Cc\0Martin Schwidefsky <schwidefsky-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>" + Heiko Carstens <heiko.carstens-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org> + Dave Hansen <dave.hansen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> + Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org> + Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org> + David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> + " Ren\303\251 Nyffenegger <mail-gLCNRsNSrVdVZEhyV+6z5nIPMjoJpjVV@public.gmane.org>" + Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> + Paul E . McKenney <paulmck-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org> + Eric W . Biederman <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org> + Oleg Nesterov <oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> + Pavel Tikhomirov <ptikhomirov-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org> + Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> + H . Peter Anvin <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org> + Andy Lutomirski <luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> + Paolo Bonzini <pbonzini-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> + Rik van Riel <riel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> + Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> + " Josh Poimboeuf <jpoimboe@redhat.c>\0" "\00:1\0" "b\0" "On Mon, 2017-05-08 at 09:52 +0200, Ingo Molnar wrote:\n" @@ -90,4 +74,4 @@ "REFCOUNT overflow checking feature, so it's something that's already\n" being done in practice elsewhere. -0d1a480b36256fedad175bc810a5eee6bd7829ae8633945dd6a600dad885c3fe +8cd11e3faa1df14912f996362e86d241200bce85eff05f1eeaa4d2d59fd48597
diff --git a/a/1.txt b/N2/1.txt index 202d73a..ecbf072 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -3,27 +3,27 @@ On Mon, 2017-05-08 at 09:52 +0200, Ingo Molnar wrote: > ... it's just not usable in that form for a regular maintenance flow. > > So what would be more useful is to add a specific Sparse check that -> only checks +> only checks? > KERNEL_DS, to add it as a regular (.config driven) build option and -> make sure the +> make sure the? > kernel build has zero warnings. > > From that point on we can declare that this kind of bug won't occur -> anymore, if +> anymore, if? > the Sparse implementation of the check is correct. > > But there's a (big) problem with that development model: Sparse is not -> part of the +> part of the? > kernel tree and adding a feature to it while making the kernel depend -> on that +> on that? > brand new feature is a logistical nightmare. The overhead is quite -> similar to +> similar to? > adding new features to a compiler - it happens at a glacial pace and -> is only done +> is only done? > for major features really, at considerable expense. I don't think this -> is an +> is an? > adequate model for 'extended syntax checking' of the kernel, -> especially when it +> especially when it? > comes to correctness that has such obvious security impact. > > Thanks, diff --git a/a/content_digest b/N2/content_digest index 897f986..f0e0c45 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -2,47 +2,10 @@ "ref\0CAJcbSZGQsRVg3QZ9QfLn2HBC+RP-7fUTab0bYDJ455d8y8GyNw@mail.gmail.com\0" "ref\020170508073352.caqe3fqf7nuxypgi@gmail.com\0" "ref\020170508075209.7aluvpwildw325rf@gmail.com\0" - "From\0Daniel Micay <danielmicay@gmail.com>\0" - "Subject\0Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode\0" + "From\0danielmicay@gmail.com (Daniel Micay)\0" + "Subject\0[kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode\0" "Date\0Mon, 08 May 2017 11:22:12 -0400\0" - "To\0Ingo Molnar <mingo@kernel.org>" - " Thomas Garnier <thgarnie@google.com>\0" - "Cc\0Martin Schwidefsky <schwidefsky@de.ibm.com>" - Heiko Carstens <heiko.carstens@de.ibm.com> - Dave Hansen <dave.hansen@intel.com> - Arnd Bergmann <arnd@arndb.de> - Thomas Gleixner <tglx@linutronix.de> - David Howells <dhowells@redhat.com> - " Ren\303\251 Nyffenegger <mail@renenyffenegger.ch>" - Andrew Morton <akpm@linux-foundation.org> - Paul E . McKenney <paulmck@linux.vnet.ibm.com> - Eric W . Biederman <ebiederm@xmission.com> - Oleg Nesterov <oleg@redhat.com> - Pavel Tikhomirov <ptikhomirov@virtuozzo.com> - Ingo Molnar <mingo@redhat.com> - H . Peter Anvin <hpa@zytor.com> - Andy Lutomirski <luto@kernel.org> - Paolo Bonzini <pbonzini@redhat.com> - Rik van Riel <riel@redhat.com> - Kees Cook <keescook@chromium.org> - Josh Poimboeuf <jpoimboe@redhat.com> - Borislav Petkov <bp@alien8.de> - Brian Gerst <brgerst@gmail.com> - Kirill A . Shutemov <kirill.shutemov@linux.intel.com> - Christian Borntraeger <borntraeger@de.ibm.com> - Russell King <linux@armlinux.org.uk> - Will Deacon <will.deacon@arm.com> - Catalin Marinas <catalin.marinas@arm.com> - Mark Rutland <mark.rutland@arm.com> - James Morse <james.morse@arm.com> - linux-s390 <linux-s390@vger.kernel.org> - LKML <linux-kernel@vger.kernel.org> - Linux API <linux-api@vger.kernel.org> - the arch/x86 maintainers <x86@kernel.org> - linux-arm-kernel@lists.infradead.org - Kernel Hardening <kernel-hardening@lists.openwall.com> - Linus Torvalds <torvalds@linux-foundation.org> - " Peter Zijlstra <a.p.zijlstra@chello.nl>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Mon, 2017-05-08 at 09:52 +0200, Ingo Molnar wrote:\n" @@ -50,27 +13,27 @@ "> ... it's just not usable in that form for a regular maintenance flow.\n" "> \n" "> So what would be more useful is to add a specific Sparse check that\n" - "> only checks\302\240\n" + "> only checks?\n" "> KERNEL_DS, to add it as a regular (.config driven) build option and\n" - "> make sure the\302\240\n" + "> make sure the?\n" "> kernel build has zero warnings.\n" "> \n" "> From that point on we can declare that this kind of bug won't occur\n" - "> anymore, if\302\240\n" + "> anymore, if?\n" "> the Sparse implementation of the check is correct.\n" "> \n" "> But there's a (big) problem with that development model: Sparse is not\n" - "> part of the\302\240\n" + "> part of the?\n" "> kernel tree and adding a feature to it while making the kernel depend\n" - "> on that\302\240\n" + "> on that?\n" "> brand new feature is a logistical nightmare. The overhead is quite\n" - "> similar to\302\240\n" + "> similar to?\n" "> adding new features to a compiler - it happens at a glacial pace and\n" - "> is only done\302\240\n" + "> is only done?\n" "> for major features really, at considerable expense. I don't think this\n" - "> is an\302\240\n" + "> is an?\n" "> adequate model for 'extended syntax checking' of the kernel,\n" - "> especially when it\302\240\n" + "> especially when it?\n" "> comes to correctness that has such obvious security impact.\n" "> \n" "> Thanks,\n" @@ -90,4 +53,4 @@ "REFCOUNT overflow checking feature, so it's something that's already\n" being done in practice elsewhere. -0d1a480b36256fedad175bc810a5eee6bd7829ae8633945dd6a600dad885c3fe +e9c39d5d88443f3b565fe250e5d1ee8e26b06b6e1ce460b775fad845bc14a189
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.