From: Ingo Molnar <mingo@elte.hu>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"yinghai@kernel.org" <yinghai@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@suse.de>,
"lkml20101129@newton.leun.net" <lkml20101129@newton.leun.net>,
stable kernel team <stable@kernel.org>,
Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>
Subject: Re: [PATCH urgent] x86: Save cr4 to mmu_cr4_features at boot time
Date: Mon, 4 Apr 2011 18:25:16 +0200 [thread overview]
Message-ID: <20110404162516.GA31241@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.1104041616550.16492@kaball-desktop>
* Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:
> On Mon, 4 Apr 2011, Ingo Molnar wrote:
> >
> > * Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:
> >
> > > Just to clarify the situation the patch "x86-64: finish cleanup_highmaps()'s
> > > job wrt. _brk_end" was backported to the stable trees [...]
> >
> > There's no commit with such a title upstream - there's not even one that is
> > close. Could you cite the sha1 you refer to?
>
> The commit id upstream is 498343967613183611ac37dccb2846496d954c06
That commit is from the v2.6.30 era:
|
| commit 498343967613183611ac37dccb2846496d954c06
| Author: Jan Beulich <jbeulich@novell.com>
| AuthorDate: Wed May 6 13:06:47 2009 +0100
| Commit: H. Peter Anvin <hpa@zytor.com>
| CommitDate: Thu May 7 21:51:34 2009 -0700
|
| x86-64: finish cleanup_highmaps()'s job wrt. _brk_end
|
... i.e. the bug is almost 2 years and 8 -stable cycles old!
Peter very consciously did not mark the fix for this commit as -stable
material. It was ineligible for -stable for multiple reasons: it by no means
fixed a 2.6.39 regression and the fix was literally just a few days old.
Thanks,
Ingo
next prev parent reply other threads:[~2011-04-04 16:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 16:38 [PATCH urgent] x86: Save cr4 to mmu_cr4_features at boot time Stefano Stabellini
2011-04-01 6:23 ` Ingo Molnar
2011-04-01 11:30 ` Stefano Stabellini
2011-04-01 18:51 ` H. Peter Anvin
2011-04-01 19:08 ` Ingo Molnar
2011-04-01 20:59 ` [stable] " Greg KH
2011-04-01 22:57 ` Stefano Stabellini
2011-04-04 15:11 ` Ingo Molnar
2011-04-04 15:47 ` Stefano Stabellini
2011-04-04 16:25 ` Ingo Molnar [this message]
2011-04-05 6:29 ` Rafael J. Wysocki
2011-04-05 6:37 ` H. Peter Anvin
2011-04-05 6:43 ` Rafael J. Wysocki
2011-04-05 6:55 ` H. Peter Anvin
2011-04-05 23:47 ` H. Peter Anvin
2011-04-06 4:34 ` Rafael J. Wysocki
2011-04-06 4:45 ` H. Peter Anvin
2011-04-11 23:04 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110404162516.GA31241@elte.hu \
--to=mingo@elte.hu \
--cc=Jeremy.Fitzhardinge@citrix.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml20101129@newton.leun.net \
--cc=stable@kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.