From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Andy Lutomirski <luto@kernel.org>
Cc: "Zhang, Ning A" <ning.a.zhang@intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: backport Rewrite sync_core() to use IRET-to-self to stable kernels?
Date: Wed, 24 Jan 2018 10:00:32 +0100 [thread overview]
Message-ID: <20180124090032.GA30613@kroah.com> (raw)
In-Reply-To: <20180123072533.GA17566@kroah.com>
On Tue, Jan 23, 2018 at 08:25:33AM +0100, gregkh@linuxfoundation.org wrote:
> On Mon, Jan 22, 2018 at 07:06:29PM -0800, Andy Lutomirski wrote:
> > On Mon, Jan 22, 2018 at 6:59 PM, Zhang, Ning A <ning.a.zhang@intel.com> wrote:
> > > hello, Greg, Andy, Thomas
> > >
> > > would you like to backport these two patches to LTS kernel?
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/include/asm/processor.h?h=v4.14.14&id=1c52d859cb2d417e7216d3e56bb7fea88444cec9
> > >
> > > x86/asm/32: Make sync_core() handle missing CPUID on all 32-bit kernels
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/include/asm/processor.h?h=v4.14.14&id=c198b121b1a1d7a7171770c634cd49191bac4477
> > >
> > > x86/asm: Rewrite sync_core() to use IRET-to-self
> > >
> >
> > I'd be in favor of backporting
> > 1c52d859cb2d417e7216d3e56bb7fea88444cec9. I see no compelling reason
> > to backport the other one, since it doesn't fix a bug. Greg, can you
> > do this?
>
> I'll work on this after this round of stable kernels are released.
Now applied, thanks.
greg k-h
prev parent reply other threads:[~2018-01-24 9:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 2:59 backport Rewrite sync_core() to use IRET-to-self to stable kernels? Zhang, Ning A
2018-01-23 3:06 ` Andy Lutomirski
2018-01-23 7:25 ` gregkh
2018-01-24 8:19 ` Zhang, Ning A
2018-01-24 9:01 ` gregkh
2018-01-25 2:22 ` Zhang, Ning A
2018-01-25 6:50 ` gregkh
2018-01-24 9:00 ` gregkh [this message]
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=20180124090032.GA30613@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=ning.a.zhang@intel.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.