[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANN689E4jXT-VA3j54h_MBgCCc9YK0o_E7PY326NnvdiHmAgFQ@mail.gmail.com>
Date: Mon, 12 Nov 2012 03:55:16 -0800
From: Michel Lespinasse <walken@...gle.com>
To: Sasha Levin <levinsasha928@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Rik van Riel <riel@...hat.com>,
Hugh Dickins <hughd@...gle.com>, linux-kernel@...r.kernel.org,
Russell King <linux@....linux.org.uk>,
Ralf Baechle <ralf@...ux-mips.org>,
Paul Mundt <lethal@...ux-sh.org>,
"David S. Miller" <davem@...emloft.net>,
Chris Metcalf <cmetcalf@...era.com>, x86@...nel.org,
William Irwin <wli@...omorphy.com>, linux-mm@...ck.org,
linux-arm-kernel@...ts.infradead.org, linux-mips@...ux-mips.org,
linux-sh@...r.kernel.org, sparclinux@...r.kernel.org,
Dave Jones <davej@...hat.com>
Subject: Re: [PATCH 03/16] mm: check rb_subtree_gap correctness
On Fri, Nov 9, 2012 at 6:13 AM, Sasha Levin <levinsasha928@...il.com> wrote:
> While fuzzing with trinity inside a KVM tools (lkvm) guest, using today's -next
> kernel, I'm getting these:
>
> [ 117.007714] free gap 7fba0dd1c000, correct 7fba0dcfb000
> [ 117.019773] map_count 750 rb -1
> [ 117.028362] ------------[ cut here ]------------
> [ 117.029813] kernel BUG at mm/mmap.c:439!
>
> Note that they are very easy to reproduce.
Thanks for the report. I had trouble reproducing this on Friday, but
after Hugh came up with an easy test case I think I have it figured
out. I sent out a proposed fix as "[PATCH 0/3] fix missing
rb_subtree_gap updates on vma insert/erase". Let's follow up the
discussion there if necessary.
Cheers,
--
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.
--
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