linux-ext4 - [Bug 71301] CPU soft lockup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 28 Feb 2014 20:42:44 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 71301] CPU soft lockup

https://bugzilla.kernel.org/show_bug.cgi?id=71301

Theodore Tso <tytso@....edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@....edu

--- Comment #1 from Theodore Tso <tytso@....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.
,\rE.): 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.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html