From: Punit Agrawal <punit.agrawal@arm.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Yury Norov <ynorov@caviumnetworks.com>,
<akpm@linux-foundation.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <steve.capper@arm.com>
Subject: Re: arm64: segfaults on next-20170602 with LTP tests
Date: Mon, 05 Jun 2017 10:35:37 +0100 [thread overview]
Message-ID: <87k24q4w0m.fsf@e105922-lin.cambridge.arm.com> (raw)
In-Reply-To: <20170602152440.GQ6371@arm.com> (Will Deacon's message of "Fri, 2 Jun 2017 16:24:41 +0100")
Will Deacon <will.deacon@arm.com> writes:
> On Fri, Jun 02, 2017 at 05:42:04PM +0300, Yury Norov wrote:
>> On Fri, Jun 02, 2017 at 03:37:51PM +0300, Yury Norov wrote:
>> > On Fri, Jun 02, 2017 at 01:19:18PM +0100, Will Deacon wrote:
>> > > Hi Yury,
>> > >
>> > > [adding Steve and Punit]
>> > >
>> > > On Fri, Jun 02, 2017 at 02:11:51PM +0300, Yury Norov wrote:
>> > > > I see that latest and yesterday's linux-next segfaults with tests pth_str01,
>> > > > pth_str03, rwtest04. Rwtest04 hangs sometimes. Crashes are not always
>> > > > reproducible. About week ago everything was fine. Kernel log and config file
>> > > > are attached. The testing is performed on qemu.
>> > >
>> > > It's weird that these haven't cropped up in our nightly tests, especially
>> > > given that defconfig is very similar to the one you're using. That said,
>> > > I see huge pmds cropping up in the traces below and there have been some
>> > > recent changes from Punit and Steve in that area, in particular things
>> > > like 55f379263bcc ("mm, gup: ensure real head page is ref-counted when using
>> > > hugepages").
>> > >
>> > > Are you in a position to bisect this, or is it too fiddly to reproduce?
>>
>> I have bisected the bug to exactly this patch. If I revert it, the
>> pth_str01/03 are passed.
>
> Thanks for doing that: I had my suspicion ;) I can also reproduce the
> failure locally on my Juno.
>
> Punit -- please can you investigate this? Otherwise I think we have to
> revert this for now and bring it back after some better testing.
Apologies for the breakage. It looks like anonymous hugepages are not
happy with the change. Let me dig into this.
>
> Will
next prev parent reply other threads:[~2017-06-05 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 11:11 Yury Norov
2017-06-02 12:19 ` Will Deacon
2017-06-02 12:37 ` Yury Norov
2017-06-02 14:42 ` Yury Norov
2017-06-02 15:24 ` Will Deacon
2017-06-05 9:35 ` Punit Agrawal [this message]
2017-06-05 11:12 ` Punit Agrawal
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=87k24q4w0m.fsf@e105922-lin.cambridge.arm.com \
--to=punit.agrawal@arm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steve.capper@arm.com \
--cc=will.deacon@arm.com \
--cc=ynorov@caviumnetworks.com \
/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
all inboxes | Powered by JetHome®