[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.00.0801081126200.3148@woody.linux-foundation.org>
Date: Tue, 8 Jan 2008 11:31:19 -0800 (PST)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Arjan van de Ven <arjan@...ux.intel.com>
cc: Randy Dunlap <randy.dunlap@...cle.com>,
Kevin Winchester <kjwinchester@...il.com>,
"J. Bruce Fields" <bfields@...ldses.org>,
Al Viro <viro@...IV.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
NetDev <netdev@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: Top 10 kernel oopses for the week ending January 5th, 2008
On Tue, 8 Jan 2008, Arjan van de Ven wrote:
>
> ok done; I had to fizzle a bit because some things aren't *exactly* a
> BUG() statement but I track them anyway (things like the "sleeping in
> invalid context" check), so I had to somewhat arbitrarily assign
> categories for those. I might fine tune these over time some; if you or
> someone else sees problems with categorization please let me know
Looking good. I wonder if we could also have some way to cross-ref these
things with the regression list (notably try to get pointers to them in
the regression list).
Right now, the regression list keeps track of the things that are closed,
but kerneloops.org obviously doesn't see that, so it's not obvious which
oopses are "uninteresting" since they've been fixed.
Linus
--
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