[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5017D882.6040007@redhat.com>
Date: Tue, 31 Jul 2012 09:07:14 -0400
From: Larry Woodman <lwoodman@...hat.com>
To: Mel Gorman <mgorman@...e.de>
CC: Rik van Riel <riel@...hat.com>, Hugh Dickins <hughd@...gle.com>,
Michal Hocko <mhocko@...e.cz>, Linux-MM <linux-mm@...ck.org>,
David Gibson <david@...son.dropbear.id.au>,
Ken Chen <kenchen@...gle.com>,
Cong Wang <xiyou.wangcong@...il.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -alternative] mm: hugetlbfs: Close race during teardown
of hugetlbfs shared page tables V2 (resend)
On 07/31/2012 08:46 AM, Mel Gorman wrote:
> On Mon, Jul 30, 2012 at 03:11:27PM -0400, Larry Woodman wrote:
>>> <SNIP>
>>> That is a surprise. Can you try your test case on 3.4 and tell us if the
>>> patch fixes the problem there? I would like to rule out the possibility
>>> that the locking rules are slightly different in RHEL. If it hits on 3.4
>>> then it's also possible you are seeing a different bug, more on this later.
>>>
>> Sorry for the delay Mel, here is the BUG() traceback from the 3.4
>> kernel with your
>> patches:
>>
>> --------------------------------------------------------------------------------------------------------------------------------------------
>> [ 1106.156569] ------------[ cut here ]------------
>> [ 1106.161731] kernel BUG at mm/filemap.c:135!
>> [ 1106.166395] invalid opcode: 0000 [#1] SMP
>> [ 1106.170975] CPU 22
>> [ 1106.173115] Modules linked in: bridge stp llc sunrpc binfmt_misc
>> dcdbas microcode pcspkr acpi_pad acpi]
>> [ 1106.201770]
> Thanks, looks very similar.
>
>> [ 1106.203426] Pid: 18001, comm: mpitest Tainted: G W
>> 3.3.0+ #4 Dell Inc. PowerEdge R620/07NDJ2
> You say this was a 3.4 kernel but the message says 3.3. Probably not
> relevant, just interesting.
>
Oh, sorry I posted the wrong traceback. I tested both 3.3 & 3.4 and had
the same results.
I'll do it again and post the 3.4 traceback for you,
Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists