[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <33968a3c7cc750f3d1cabf062f5fb25fd176e816.camel@intel.com>
Date: Fri, 22 Feb 2019 18:32:22 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "bp@...en8.de" <bp@...en8.de>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>,
"ard.biesheuvel@...aro.org" <ard.biesheuvel@...aro.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"nadav.amit@...il.com" <nadav.amit@...il.com>,
"Dock, Deneen T" <deneen.t.dock@...el.com>,
"linux-security-module@...r.kernel.org"
<linux-security-module@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"hpa@...or.com" <hpa@...or.com>,
"kristen@...ux.intel.com" <kristen@...ux.intel.com>,
"mingo@...hat.com" <mingo@...hat.com>,
"linux_dti@...oud.com" <linux_dti@...oud.com>,
"luto@...nel.org" <luto@...nel.org>,
"will.deacon@....com" <will.deacon@....com>,
"kernel-hardening@...ts.openwall.com"
<kernel-hardening@...ts.openwall.com>
Subject: Re: [PATCH v3 00/20] Merge text_poke fixes and executable lockdowns
On Fri, 2019-02-22 at 17:14 +0100, Borislav Petkov wrote:
> On Thu, Feb 21, 2019 at 03:44:31PM -0800, Rick Edgecombe wrote:
> > Changes v2 to v3:
> > - Fix commit messages and comments [Boris]
> > - Rename VM_HAS_SPECIAL_PERMS [Boris]
> > - Remove unnecessary local variables [Boris]
> > - Rename set_alias_*() functions [Boris, Andy]
> > - Save/restore DR registers when using temporary mm
> > - Move line deletion from patch 10 to patch 17
>
> In your previous submission there was a patch called
>
> Subject: [PATCH v2 01/20] Fix "x86/alternatives: Lockdep-enforce text_mutex in
> text_poke*()"
>
> What happened to it?
>
> It did introduce a function text_poke_kgdb(), a.o., and I see this
> function in the diff contexts in some of the patches in this submission
> so it looks to me like you missed that first patch when submitting v3?
>
> Or am *I* missing something?
>
> Thx.
>
Oh, you are right! Sorry about that. I'll just send a new version with fixes for
other comments instead of a resend of this one.
Thanks,
Rick
Powered by blists - more mailing lists