From: David Gibson <david@gibson.dropbear.id.au>
To: gregkh@suse.de
Cc: stable-commits@vger.kernel.org, paulus@samba.org,
linuxppc-dev@ozlabs.org
Subject: Re: patch powerpc-fix-size-check-for-hugetlbfs.patch queued to -stable tree
Date: Tue, 14 Aug 2007 16:45:34 +1000 [thread overview]
Message-ID: <20070814064534.GE8791@localhost.localdomain> (raw)
In-Reply-To: <20070813234218.4796D14540D0@imap.suse.de>
On Mon, Aug 13, 2007 at 04:26:27PM -0700, gregkh@suse.de wrote:
>
> This is a note to let you know that we have just queued up the patch titled
>
> Subject: powerpc: Fix size check for hugetlbfs
>
> to the 2.6.22-stable tree. Its filename is
>
> powerpc-fix-size-check-for-hugetlbfs.patch
>
> A git repo of this tree can be found at
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
>
> >From benh@kernel.crashing.org Mon Aug 13 16:17:09 2007
> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Date: Wed, 08 Aug 2007 15:44:15 +1000
> Subject: powerpc: Fix size check for hugetlbfs
> To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
> Cc: Paul Mackerras <paulus@samba.org>, stable@kernel.org
> Message-ID: <1186551855.938.164.camel@localhost.localdomain>
>
> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>
> My "slices" address space management code that was added in 2.6.22
> implementation of get_unmapped_area() doesn't properly check that the
> size is a multiple of the requested page size. This allows userland to
> create VMAs that aren't a multiple of the huge page size with hugetlbfs
> (since hugetlbfs entirely relies on get_unmapped_area() to do that
> checking) which leads to a kernel BUG() when such areas are torn down.
Ok, I said I was going to look into a libhugetlbfs testcase for this.
Doesn't appear there's specifically a testcase for misaligned size -
I'll add one.
However, it seems the current kernel, on ppc64, gives a testcase
failure on 'misaligned_offset', because it's not failing a mapping
with a non-hugepage aligned file offset. I'm not sure (yet) if this
failure is also caused by the new slice code, but it seems a likely
candidate.
Still investigating...
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-08-14 6:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 5:44 [PATCH] powerpc: Fix size check for hugetlbfs Benjamin Herrenschmidt
2007-08-13 23:26 ` patch powerpc-fix-size-check-for-hugetlbfs.patch queued to -stable tree gregkh
2007-08-14 6:45 ` David Gibson [this message]
2007-08-14 7:48 ` David Gibson
2007-08-16 3:53 ` David Gibson
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=20070814064534.GE8791@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=gregkh@suse.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=stable-commits@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.