public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-ext4@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kerneloops.org: 2.6.26-rc possible regression in ext3
Date: Thu, 19 Jun 2008 09:17:13 -0500	[thread overview]
Message-ID: <485A6A69.8090402@redhat.com> (raw)
In-Reply-To: <485A680B.3020004@linux.intel.com>

Arjan van de Ven wrote:
> 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.

Ok, that was my guess.  I'll shoot you an email next time.  :)

Thanks,
-Eric

  reply	other threads:[~2008-06-19 14:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19  5:36 kerneloops.org: 2.6.26-rc possible regression in ext3 Arjan van de Ven
2008-06-19  5:42 ` Dave Airlie
2008-06-19  5:48   ` Arjan van de Ven
2008-06-19  6:42   ` Linus Torvalds
2008-06-19  7:09     ` Arjan van de Ven
2008-06-19  8:11   ` Adrian Bunk
2008-06-19  8:32     ` Mikael Pettersson
2008-06-19 10:49       ` Adrian Bunk
2008-06-19 13:40     ` Arjan van de Ven
2008-06-19 15:10       ` Adrian Bunk
2008-06-19 15:18         ` Arjan van de Ven
2008-06-19 15:25           ` Adrian Bunk
2008-06-19 15:27             ` Arjan van de Ven
2008-06-19 15:43               ` Adrian Bunk
2008-06-19 14:00 ` Eric Sandeen
2008-06-19 14:07   ` Arjan van de Ven
2008-06-19 14:17     ` Eric Sandeen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-19  5:34 Arjan van de Ven
2008-06-19  6:01 ` Linus Torvalds
2008-06-19  6:09   ` Arjan van de Ven
2008-06-19  6:12   ` Arjan van de Ven
2008-06-19  6:14   ` Linus Torvalds
2008-06-19  6:40     ` Linus Torvalds
2008-06-20 15:34   ` Bill Nottingham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=485A6A69.8090402@redhat.com \
    --to=sandeen@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox