All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Punit Agrawal <punit.agrawal@arm.com>
Cc: stable@vger.kernel.org, ioana.ciornei@nxp.com,
	Marc Zyngier <marc.zyngier@arm.com>,
	Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [PATCH] KVM: arm/arm64: Fix check for hugepage size when allocating at Stage 2
Date: Wed, 28 Feb 2018 18:45:30 +0100	[thread overview]
Message-ID: <20180228174530.GA24853@kroah.com> (raw)
In-Reply-To: <20180228164009.3907-1-punit.agrawal@arm.com>

On Wed, Feb 28, 2018 at 04:40:09PM +0000, Punit Agrawal wrote:
> Commit 45ee9d5e97a4 ("KVM: arm/arm64: Check pagesize when allocating a
> hugepage at Stage 2") lost the check for PMD_SIZE during the backport
> to 4.9.
> 
> Fix this by correcting the condition to detect hugepages during stage
> 2 allocation.
> 
> Fixes: 45ee9d5e97a4 ("KVM: arm/arm64: Check pagesize when allocating a hugepage at Stage 2")
> Reported-by: Ioana Ciornei <ioana.ciornei@nxp.com>
> Signed-off-by: Punit Agrawal <punit.agrawal@arm.com>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Christoffer Dall <christoffer.dall@linaro.org>
> --
> Hi Greg,
> 
> This patch fixes a commit in the stable tree that was backported from
> upstream. I am not sure what the tag convention is for such a commit -
> so sending as a fix.

What you did here was just fine, now queued up, thanks.

greg k-h

      parent reply	other threads:[~2018-02-28 17:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28 16:40 [PATCH] KVM: arm/arm64: Fix check for hugepage size when allocating at Stage 2 Punit Agrawal
2018-02-28 17:45 ` Patch "KVM: arm/arm64: Fix check for hugepage size when allocating at Stage 2" has been added to the 4.9-stable tree gregkh
2018-02-28 17:45 ` Greg KH [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=20180228174530.GA24853@kroah.com \
    --to=greg@kroah.com \
    --cc=christoffer.dall@linaro.org \
    --cc=ioana.ciornei@nxp.com \
    --cc=marc.zyngier@arm.com \
    --cc=punit.agrawal@arm.com \
    --cc=stable@vger.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.