From: Arjan van de Ven Subject: Re: kerneloops.org: 2.6.26-rc possible regression in ext3 Date: Thu, 19 Jun 2008 07:07:07 -0700 Message-ID: <485A680B.3020004@linux.intel.com> References: <4859F075.2050207@linux.intel.com> <485A668D.3050306@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Linux Kernel Mailing List , Linus Torvalds , linux-ext4@vger.kernel.org, Andrew Morton To: Eric Sandeen Return-path: Received: from mga06.intel.com ([134.134.136.21]:18059 "EHLO orsmga101.jf.intel.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752764AbYFSOHW (ORCPT ); Thu, 19 Jun 2008 10:07:22 -0400 In-Reply-To: <485A668D.3050306@redhat.com> Sender: linux-ext4-owner@vger.kernel.org List-ID: Eric Sandeen wrote: > Arjan van de Ven wrote: >> In the kerneloops.org stats, a new oops is rapidly climbing the charts. >> The oops is a page fault in the ext3 "do_slit" function, and the first >> report of it was with 2.6.26-rc6-git3. >> >> It happens with various applications; the backtraces are at: >> >> http://www.kerneloops.org/search.php?search=do_split > > Arjan, I was just looking at kerneloops last night, seeing the count for > this oops climb, and was wishing there were some way to annotate an oops > signature with more info. If I could have tagged this with the RH > bugzilla nr. it might have saved a lot of time for folks. Is this > feasible? Or is finding the oops text in bugzilla the only way? > there's a way to add a description to oopses (you might have seen some of these descriptions already); however I've not implemented an account system yet so for now it's only me who can add these.