From: Arjan van de Ven <arjan@linux.intel.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-ext4@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: kerneloops.org: 2.6.26-rc possible regression in ext3
Date: Wed, 18 Jun 2008 22:36:53 -0700 [thread overview]
Message-ID: <4859F075.2050207@linux.intel.com> (raw)
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
but are generally of this pattern:
*do_split
ext3_add_entry
ext3_rename
vfs_rename
... <various paths into vfs_rename> ...
or
*do_split
? add_dirent_to_buf
ext3_add_entry
ext3_new_inode
ext3_add_nondir
ext3_create
vfs_create
....
did we change anything in ext
next reply other threads:[~2008-06-19 5:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 5:36 Arjan van de Ven [this message]
2008-06-19 5:42 ` kerneloops.org: 2.6.26-rc possible regression in ext3 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
-- 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=4859F075.2050207@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--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