diff for duplicates of <20180424145104.GC3125@cisco> diff --git a/a/1.txt b/N1/1.txt index e6d17c7..5927829 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -4,7 +4,7 @@ On Tue, Apr 24, 2018 at 11:46:38PM +0900, Tetsuo Handa wrote: > > > > + WARN(1, "big key algorithm changed?"); > > Please avoid using WARN() WARN_ON() etc. -> syzbot would catch it and panic() due to panic_on_warn == 1. +> syzbot would catch it and panic() due to panic_on_warn = 1. But it is really a programming bug in this case (and it seems better than BUG()...). Isn't this exactly the sort of case we want to catch? diff --git a/a/content_digest b/N1/content_digest index 0b95cdf..52b0aef 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,7 +4,7 @@ "ref\0201804242346.FHI69745.SQMHFVOOFLFOJt@I-love.SAKURA.ne.jp\0" "From\0Tycho Andersen <tycho@tycho.ws>\0" "Subject\0Re: [PATCH 1/3] big key: get rid of stack array allocation\0" - "Date\0Tue, 24 Apr 2018 08:51:04 -0600\0" + "Date\0Tue, 24 Apr 2018 14:51:04 +0000\0" "To\0Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>\0" "Cc\0ebiggers3@gmail.com" dhowells@redhat.com @@ -23,11 +23,11 @@ "> > > > +\t\tWARN(1, \"big key algorithm changed?\");\n" "> \n" "> Please avoid using WARN() WARN_ON() etc.\n" - "> syzbot would catch it and panic() due to panic_on_warn == 1.\n" + "> syzbot would catch it and panic() due to panic_on_warn = 1.\n" "\n" "But it is really a programming bug in this case (and it seems better\n" "than BUG()...). Isn't this exactly the sort of case we want to catch?\n" "\n" Tycho -1844cf7fa99d82a9d250ee56ef57ce3a2a05e49c58e41d5332e07fcc383a5764 +9325166b7067e0f237a82d91410a1b899fd92e50185efcc402eb3eec54156e30
diff --git a/a/1.txt b/N2/1.txt index e6d17c7..5613329 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -10,3 +10,7 @@ But it is really a programming bug in this case (and it seems better than BUG()...). Isn't this exactly the sort of case we want to catch? Tycho +-- +To unsubscribe from this list: send the line "unsubscribe linux-security-module" in +the body of a message to majordomo at vger.kernel.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N2/content_digest index 0b95cdf..5a0a27c 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -2,19 +2,10 @@ "ref\020180424045015.GA4281@sol.localdomain\0" "ref\020180424143539.GB3125@cisco\0" "ref\0201804242346.FHI69745.SQMHFVOOFLFOJt@I-love.SAKURA.ne.jp\0" - "From\0Tycho Andersen <tycho@tycho.ws>\0" - "Subject\0Re: [PATCH 1/3] big key: get rid of stack array allocation\0" + "From\0tycho@tycho.ws (Tycho Andersen)\0" + "Subject\0[PATCH 1/3] big key: get rid of stack array allocation\0" "Date\0Tue, 24 Apr 2018 08:51:04 -0600\0" - "To\0Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>\0" - "Cc\0ebiggers3@gmail.com" - dhowells@redhat.com - keyrings@vger.kernel.org - linux-security-module@vger.kernel.org - linux-kernel@vger.kernel.org - kernel-hardening@lists.openwall.com - jmorris@namei.org - serge@hallyn.com - " Jason@zx2c4.com\0" + "To\0linux-security-module@vger.kernel.org\0" "\00:1\0" "b\0" "On Tue, Apr 24, 2018 at 11:46:38PM +0900, Tetsuo Handa wrote:\n" @@ -28,6 +19,10 @@ "But it is really a programming bug in this case (and it seems better\n" "than BUG()...). Isn't this exactly the sort of case we want to catch?\n" "\n" - Tycho + "Tycho\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-security-module\" in\n" + "the body of a message to majordomo at vger.kernel.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -1844cf7fa99d82a9d250ee56ef57ce3a2a05e49c58e41d5332e07fcc383a5764 +92ce7547944fc901053d6560f859460fbea2e855e7d8bd50a398118d6ffa23e9
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.