linux-kernel - Re: [PATCH 1/2] x86/mce: Only restart instruction after machine check recovery if it is safe

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: <CA+8MBbKr-dc2MFNCvthqWzy3MvQmb8UEKy74mi36BkYHLDTOPg@mail.gmail.com>
Date:	Mon, 14 May 2012 11:02:59 -0700
From:	Tony Luck <tony.luck@...el.com>
To:	Borislav Petkov <bp@...64.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Chen Gong <gong.chen@...ux.intel.com>,
	"Huang, Ying" <ying.huang@...el.com>,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
Subject: Re: [PATCH 1/2] x86/mce: Only restart instruction after machine check
 recovery if it is safe

On Mon, May 14, 2012 at 10:17 AM, Borislav Petkov <bp@...64.org> wrote:
> I was wondering about that but don't have any other flags/use cases.
> Well, we can always change it later if needed.

So is that an Ack? I was thinking that I should send this part to
Linus now ... since restarting from a fault when RIPV isn't set
could result in an application doing something bad (like getting
the wrong answer).

The instruction stuff is new and needs to wait for the merge window.

-Tony
--
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/