From: Ben Hutchings <ben@decadent.org.uk>
To: Paul Mackerras <paulus@samba.org>
Cc: Hillf Danton <dhillf@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
David Gibson <david@gibson.dropbear.id.au>,
stable@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: Please include commit 90481622d7 in 3.3-stable
Date: Sat, 26 May 2012 22:37:40 +0100 [thread overview]
Message-ID: <1338068260.20487.35.camel@deadeye> (raw)
In-Reply-To: <1336811645.8274.496.camel@deadeye>
[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]
On Sat, 2012-05-12 at 09:34 +0100, Ben Hutchings wrote:
> On Thu, 2012-05-10 at 19:58 +1000, Paul Mackerras wrote:
> > Please include commit 90481622d7 ("hugepages: fix use after free bug
> > in "quota" handling") from Linus' tree in the next 3.3 stable release.
> > It applies without fuzz, though with offsets.
> >
> > It fixes a use-after-free bug in the huge page code that we are
> > hitting when using KVM on IBM Power machines with large pages backing
> > the guests, though it can in principle be hit in other ways also.
> > Since it's a use-after-free bug, it tends to result in an immediate
> > kernel crash if you have slab debug turned on, or occasional
> > hard-to-debug memory corruption if you don't.
> >
> > The bug is also present in earlier kernels, and the patch should
> > apply at least to 3.2. It would be good if it can be applied to
> > earlier kernels also.
>
> I tried cherry-picking this on top of 3.2.17, but there was a conflict
> in unmap_ref_private(). It looks like all of these belong in 3.2.y as
> well:
>
> 1e16a53 mm/hugetlb.c: fix virtual address handling in hugetlb fault
> 0c176d5 mm: hugetlb: fix pgoff computation when unmapping page from vma
> ea5768c mm/hugetlb.c: avoid bogus counter of surplus huge page
> 409eb8c mm/hugetlb.c: undo change to page mapcount in fault handler
> cd2934a flush_tlb_range() needs ->page_table_lock when ->mmap_sem is not held
Sorry, I didn't make myself clear. I'm asking for confirmation: should
these all be applied to 3.2.y?
Ben.
--
Ben Hutchings
You can't have everything. Where would you put it?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-05-26 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120510095837.GB16271@bloggs.ozlabs.ibm.com>
2012-05-12 8:34 ` Please include commit 90481622d7 in 3.3-stable Ben Hutchings
2012-05-26 21:37 ` Ben Hutchings [this message]
2012-05-29 5:46 ` Paul Mackerras
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=1338068260.20487.35.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=akpm@linux-foundation.org \
--cc=david@gibson.dropbear.id.au \
--cc=dhillf@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=paulus@samba.org \
--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 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).