linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zhang, Ning A" <ning.a.zhang@intel.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	Andy Lutomirski <luto@kernel.org>
Cc: "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 08:19:44 +0000	[thread overview]
Message-ID: <027FCDD209E4CC4181A7B9D5DBB880575FDD9DEC@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20180123072533.GA17566@kroah.com>

Thanks Greg, Andy

How about c198b121b1a1d7a7171770c634cd49191bac4477?
Will both patches go to stable kernel?

BR.
Ning.

-----Original Message-----
From: gregkh@linuxfoundation.org [mailto:gregkh@linuxfoundation.org] 
Sent: Tuesday, January 23, 2018 3:26 PM
To: Andy Lutomirski <luto@kernel.org>
Cc: Zhang, Ning A <ning.a.zhang@intel.com>; tglx@linutronix.de; stable@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: backport Rewrite sync_core() to use IRET-to-self to stable kernels?

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=1c52d859cb
> > 2d417e7216d3e56bb7fea88444cec9
> >
> > 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=c198b121b1
> > a1d7a7171770c634cd49191bac4477
> >
> > 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.

thanks,

greg k-h

  reply	other threads:[~2018-01-24  8:19 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 [this message]
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

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=027FCDD209E4CC4181A7B9D5DBB880575FDD9DEC@SHSMSX104.ccr.corp.intel.com \
    --to=ning.a.zhang@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).