linux-kernel - Re: [GIT PULL] x86/mce fix (ready for 3.6 merge window)

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+8MBbJjhVgEM7bJzZOSFvT6+RBLUQV6KtdzShuBxBH_nDxo4w@mail.gmail.com>
Date:	Wed, 11 Jul 2012 09:26:13 -0700
From:	Tony Luck <tony.luck@...el.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	linux-kernel@...r.kernel.org, Borislav Petkov <bp@...en8.de>,
	"the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: [GIT PULL] x86/mce fix (ready for 3.6 merge window)

On Wed, Jul 11, 2012 at 1:04 AM, Ingo Molnar <mingo@...nel.org> wrote:
>  - If it's for v3.6 then the Cc: stable backport is not
>    justified. Either it's for tip:x86/urgent and then we'll
>    merge it straight away, or for tip:x86/mce for v3.6 and then
>    there's no Cc: stable tag.

The commit that this fixes was included in 3.4 - so I was thinking that this
should be backported to stable 3.4 ... but 3.4 isn't a long term release, so
it will be abandoned when 3.5 is released.

Since we are at -rc6 and this isn't a regression from the current merge,
I figured that it wasn't a candidate for immediate merge ... hence the
3.6 request. So it would appear that there isn't a way that this can make
it back to 3.4-stable.

I'll fix up all the other stuff and send a new pull (still for 3.6,
and still with
a Cc: stable for backport to 3.5)

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