linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Greg KH <gregkh@linuxfoundation.org>, Andi Kleen <andi@firstfloor.org>
Cc: stable@vger.kernel.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, bernhard.kaindl@thalesgroup.com,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] x86/mm/pat: Fix L1TF stable backport for CPA
Date: Mon, 17 Sep 2018 14:16:33 +0200	[thread overview]
Message-ID: <0263c7cf-dafb-012a-78af-9b9f8e4a57fe@suse.cz> (raw)
In-Reply-To: <20180917115151.GJ13057@kroah.com>

On 09/17/2018, 01:51 PM, Greg KH wrote:
> On Thu, Sep 06, 2018 at 01:27:49PM -0700, Andi Kleen wrote:
>>> And what about populate_pud?
>>>                 set_pud(pud, pud_mkhuge(pfn_pud(cpa->pfn,
>>>                                    canon_pgprot(pud_pgprot))));
>>>
>>>                 start     += PUD_SIZE;
>>>                 cpa->pfn  += PUD_SIZE;
>>
>> Yes you're right. That case needs to be fixed too.
>>
>> Are you sending a patch, or should I?
> 
> Someone needs to.  Please?

You already released 4.4.x with the patch :):

commit 15898df477269c981dc1ae5afa39e1bb65e1db0a
Author: Jiri Slaby <jslaby@suse.cz>
Date:   Fri Sep 7 11:13:07 2018 +0200

    x86/mm/pat: Fix L1TF stable backport for CPA, 2nd call

thanks,
-- 
js
suse labs

  reply	other threads:[~2018-09-17 12:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-25 13:50 [PATCH] x86/mm/pat: Fix L1TF stable backport for CPA Andi Kleen
2018-08-25 15:07 ` Greg KH
2018-08-26  4:46 ` Guenter Roeck
2018-08-26  5:06   ` Andi Kleen
2018-08-26  5:55     ` Greg KH
2018-09-06  6:48 ` Jiri Slaby
2018-09-06 20:27   ` Andi Kleen
2018-09-17 11:51     ` Greg KH
2018-09-17 12:16       ` Jiri Slaby [this message]
2018-09-17 12:20         ` 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=0263c7cf-dafb-012a-78af-9b9f8e4a57fe@suse.cz \
    --to=jslaby@suse.cz \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=bernhard.kaindl@thalesgroup.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=x86@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 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).