[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180624071105.GA29407@gmail.com>
Date: Sun, 24 Jun 2018 09:11:05 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: linux-crypto@...r.kernel.org, Mike Galbraith <efault@....de>,
Alexey Dobriyan <adobriyan@...il.com>,
torvalds@...ux-foundation.org, tglx@...utronix.de,
jpoimboe@...hat.com, luto@...nel.org, peterz@...radead.org,
brgerst@...il.com, hpa@...or.com, linux-kernel@...r.kernel.org,
dvlasenk@...hat.com, h.peter.anvin@...el.com,
linux-tip-commits <linux-tip-commits@...r.kernel.org>,
Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: [PATCH] x86/crypto: Add missing RETs
* Borislav Petkov <bp@...en8.de> wrote:
> Lemme send a proper patch now...
>
> ---
> From: Borislav Petkov <bp@...e.de>
> Date: Sun, 17 Jun 2018 13:57:42 +0200
> Subject: [PATCH] x86/crypto: Add missing RETs
>
> Add explicit RETs to the tail calls of AEGIS and MORUS crypto algorithms
> otherwise they run into INT3 padding due to
>
> 51bad67ffbce ("x86/asm: Pad assembly functions with INT3 instructions")
>
> leading to spurious debug exceptions.
>
> Mike Galbraith <efault@....de> took care of all the remaining callsites.
Note that 51bad67ffbce has been zapped because it caused too many problems like
this, but the explicit RETs make sense nevertheless. When applying the patch
please don't include the SHA1 of the non-upstream (and probably never-upstream)
commit.
Thanks,
Ingo
Powered by blists - more mailing lists