From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 71301] CPU soft lockup
Date: Fri, 28 Feb 2014 20:42:44 +0000 [thread overview]
Message-ID: <bug-71301-13602-TULW35sHUp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71301-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=71301
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
--- Comment #1 from Theodore Tso <tytso@mit.edu> ---
It looks like a wild pointer which corrupted kernel memory. This can be seen
in the device name being garbage in the ext4_error message:
Feb 26 20:11:18 didactylos kernel: [24848.293159] EXT4-fs error (device >fA\x17
,\rE\x19): ext4_map_blocks:582: inode #64881109: block 259531249: comm du: lblock
0 mapped to illegal pblock (length 1)
Also, the BUG_ON in the timer.c:732 is caused by the timer function
sb->s_err_report.function being zero. But this is initialized when the file
system is mounted, and it's never changed by the ext4 code.
So the bug looks like it could be anywhere in the kernel, and it was just that
the memory that the wild pointer corruption happened to corrupt this time
around was in ext4's data structure.
Are you seeing any other problems with your kernel? Can you reliably reproduce
any of them?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-02-28 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 16:28 [Bug 71301] New: CPU soft lockup bugzilla-daemon
2014-02-28 20:42 ` bugzilla-daemon [this message]
2014-03-01 6:53 ` [Bug 71301] " bugzilla-daemon
2014-03-02 13:55 ` bugzilla-daemon
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=bug-71301-13602-TULW35sHUp@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).