[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 12 Oct 2018 01:15:01 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Jann Horn <jannh@...gle.com>
cc: Kees Cook <keescook@...omium.org>, Andy Lutomirski <luto@...nel.org>,
kristen@...ux.intel.com,
Kernel Hardening <kernel-hardening@...ts.openwall.com>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H . Peter Anvin" <hpa@...or.com>,
the arch/x86 maintainers <x86@...nel.org>,
kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: entry: flush the cache if syscall error
On Thu, 11 Oct 2018, Jann Horn wrote:
> On Thu, Oct 11, 2018 at 10:56 PM Kees Cook <keescook@...omium.org> wrote:
> > Seems like just changing this with "ax == 0" into "ax >= 0" would solve that?
>
> As spender points out on twitter
> (https://twitter.com/grsecurity/status/1050497259937370118 - thanks,
> spender!), struct pt_regs stores register values as "unsigned long",
> and so you'll need to use something like IS_ERR_VALUE().
Ha, so it's not only me who noticed, but then I'm not reading twitter...
Thanks,
tglx
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
