linux-kernel - Re: [GIT PULL] please pull one bug fix for v4.4

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] [day] [month] [year] [list]

Message-ID: <CAO6TR8WU49vj2FpRu=i40-iDYsUPyOpRtBE6_EwPaBbbGoh2jA@mail.gmail.com>
Date:	Mon, 11 Jan 2016 14:30:38 -0700
From:	Jeff Merkey <linux.mdb@...il.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andy Lutomirski <luto@...capital.net>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, X86 ML <x86@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Andy Lutomirski <luto@...nel.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Borislav Petkov <bp@...en8.de>, Jiri Olsa <jolsa@...nel.org>
Subject: Re: [GIT PULL] please pull one bug fix for v4.4

On 1/11/16, Thomas Gleixner <tglx@...utronix.de> wrote:
> On Mon, 11 Jan 2016, Linus Torvalds wrote:
>
>> The merge window is open, so I started looking at this that I had
>> ignored as being too late last time..
>>
>> On Sun, Dec 13, 2015 at 7:02 PM, Jeff Merkey <linux.mdb@...il.com> wrote:
>> > Patch address with email included:
>> >
>> > https://github.com/jeffmerkey/linux/commit/e1d3c76814c839a835286843f0bca33b0c5d0dd8.patch
>>
>> So at a minimum, I'd like a sign-off for the patch. But also, can you
>> describe how to actually trigger the problem? Is this actually
>> triggerable without an ICE?
>
> This patch has been discussed and the version above has issues. It's still
> not
> decided how we are going to deal with that.
>
> Thanks,
>
> 	tglx
>

Thank you for the prompt reply.  It's a complex issue in a heavily
traversed and stable code path.  That being said, the fix is trivial
and non-intrusive.

Jeff