[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5346AD92.2080705@oracle.com>
Date: Thu, 10 Apr 2014 10:41:22 -0400
From: Sasha Levin <sasha.levin@...cle.com>
To: Dave Jones <davej@...hat.com>, Bob Liu <lliubbo@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Andrea Arcangeli <aarcange@...hat.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Vlastimil Babka <vbabka@...e.cz>
Subject: Re: mm: kernel BUG at mm/huge_memory.c:1829!
On 04/10/2014 10:37 AM, Dave Jones wrote:
> On Thu, Apr 10, 2014 at 04:45:58PM +0800, Bob Liu wrote:
> > On Tue, Apr 8, 2014 at 10:37 PM, Sasha Levin <sasha.levin@...cle.com> wrote:
> > > Hi all,
> > >
> > > While fuzzing with trinity inside a KVM tools guest running the latest -next
> > > kernel, I've stumbled on the following:
> > >
> >
> > Wow! There are so many huge memory related bugs recently.
> > AFAIR, there were still several without fix. I wanna is there any
> > place can track those bugs instead of lost in maillist?
> > It seems this link is out of date
> > http://codemonkey.org.uk/projects/trinity/bugs-unfixed.php
>
> It got to be too much for me to track tbh.
> Perhaps this is one of the cases where using bugzilla.kernel.org might
> be a useful thing ?
FWIW, I'd be happy to use something else besides having to track mail
threads and keep a list of "to-do open issues".
If folks want to start using bugzilla.kernel.org for mm/ issues I'll go
ahead and enter all the open issues in there.
Thanks,
Sasha
--
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