lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrWeFrQK1bvA-aa=-=33S20vYg0O4UJ1zrdgHESZXrCpYQ@mail.gmail.com>
Date:	Mon, 21 Sep 2015 12:14:48 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	Andy Lutomirski <luto@...nel.org>
Cc:	X86 ML <x86@...nel.org>, Sasha Levin <sasha.levin@...cle.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] x86: NMI vs paravirt fixes

On Sun, Sep 20, 2015 at 4:32 PM, Andy Lutomirski <luto@...nel.org> wrote:
> These are for x86/urgent.
>
> This fixes at least one problem that Sasha can trigger using some
> crazy configuration + Trinity.  I can't reproduce the full file of
> nastiness that he's seeing, but these patches both look legit to me,
> they fix what look like real bugs, and they seem to help Sasha's
> tests.
>
> Patch 1 is ugly.  Feel free to tell me to shove the asm into the
> entry asm files, although that will involve duplicating it for
> 32-bit and 64-bit kernels.

It turns out that Sasha had noreplace-paravirt on, which is probably
how he was able to hit these reliably.

They're still bugs, though.

--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ