From: dwoods@mellanox.com (David Woods)
To: linux-arm-kernel@lists.infradead.org
Subject: BUG in HugeTLBFS with Contiguous hint
Date: Thu, 10 Mar 2016 17:23:18 -0500 [thread overview]
Message-ID: <56E1F3D6.9020906@mellanox.com> (raw)
In-Reply-To: <CAPvkgC1Oe=AiDDwSO_38bz_7FPwg3XoHK_Tts_UPorexkgFnhA@mail.gmail.com>
On 03/10/2016 02:57 AM, Steve Capper wrote:
> Hi,
> Replying to both inline below:
>
> On 9 March 2016 at 23:01, David Woods <dwoods@mellanox.com> wrote:
>> On 03/09/2016 10:31 AM, Will Deacon wrote:
>>> On Wed, Mar 09, 2016 at 02:12:56AM +0000, Steve Capper wrote:
>>>> Hi,
>>> Hi Steve,
>>>
>>>> I am very sorry for the very late bug report. I have just come across
>>>> this error.
>>>>
>>>> Whilst testing something else, I found that 2MB HugeTLB pages formed
>>>> from contiguous pte's cause BUGs to appear when running through the
>>>> libhugetlbfs test suite.
>>> Ouch. Any idea why this wasn't spotted earlier? Did something else
>>> change?
> Sorry, no. A lot of stuff has changed (and I need to double check my
> .config too). I will be able to dig into this in more detail when I
> get back in the office next week (I have a painfully slow internet
> connection to my devboard at the moment).
I was able to verify that this is a regression. I did a git bisect to
track it down and it looks like the commit which caused this failure was
61f5d698 mm: re-enable THP. The BUG does go away if
TRANSPARENT_HUGEPAGE is disabled. I believe that means the problem came
with any one of the 25 commits between 61f5d698 and 56a17b88 mm:
temporarily mark THP broken. I'll continue to try to debug it.
-Dave
prev parent reply other threads:[~2016-03-10 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 2:12 BUG in HugeTLBFS with Contiguous hint Steve Capper
2016-03-09 15:31 ` Will Deacon
2016-03-09 16:01 ` David Woods
2016-03-10 7:57 ` Steve Capper
2016-03-10 22:23 ` David Woods [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=56E1F3D6.9020906@mellanox.com \
--to=dwoods@mellanox.com \
--cc=linux-arm-kernel@lists.infradead.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.