[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <505D668C.7010206@suse.cz>
Date: Sat, 22 Sep 2012 09:19:40 +0200
From: Jiri Slaby <jslaby@...e.cz>
To: Hugh Dickins <hughd@...gle.com>
CC: Michel Lespinasse <walken@...gle.com>,
Sasha Levin <levinsasha928@...il.com>, linux-mm@...ck.org,
riel@...hat.com, peterz@...radead.org, aarcange@...hat.com,
daniel.santos@...ox.com, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, Dave Jones <davej@...hat.com>
Subject: Re: [PATCH 6/7] mm: add CONFIG_DEBUG_VM_RB build option
On 09/16/2012 09:07 PM, Hugh Dickins wrote:
>> What was the way that
>> Hugh used to reproduce the other issue?
>
> I've lost track of which issue is "other".
The other was meant to be the BUG I hit.
> To reproduce Sasha's interval_tree.c warnings, all I had to do was switch
> on CONFIG_DEBUG_VM_RB (I regret not having done so before) and boot up.
>
> I didn't look to see what was doing the mremap which caused the warning
> until now: surprisingly, it's microcode_ctl. I've not made much effort
> to get the right set of sources and work out why that would be using
> mremap (a realloc inside a library?).
>
> I failed to reproduce your BUG in huge_memory.c, but what I was trying
> was SuSE update via yast2, on several machines; but perhaps because
> they were all fairly close to up-to-date, I didn't hit a problem.
> (That was before I turned on DEBUG_VM_RB for Sasha's.)
The good news are that I cannot reproduce either with the patch applied.
thanks,
--
js
suse labs
--
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