linux-kernel - hard lockup, followed by ext4_lookup: deleted inode referenced: 524788

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-next>] [day] [month] [year] [list]

Message-ID: <20090928191644.GR12922@hexapodia.org>
Date:	Mon, 28 Sep 2009 12:16:44 -0700
From:	Andy Isaacson <adi@...apodia.org>
To:	linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org
Subject: hard lockup, followed by ext4_lookup: deleted inode referenced: 524788

After a hard lockup and reboot, my test box (running recent Linus git
851b147) came up with:

[    5.016854] EXT4-fs (sda1): mounted filesystem with ordered data mode
[    8.809125] EXT4-fs (sda1): internal journal on sda1:8
[   10.165239] EXT4-fs error (device sda1): ext4_lookup: deleted inode referenced: 524788
[   10.165286] Aborting journal on device sda1:8.
[   10.168111] EXT4-fs error (device sda1): ext4_journal_start_sb: Detected aborted journal
[   10.168169] EXT4-fs (sda1): Remounting filesystem read-only
[   10.171614] EXT4-fs (sda1): Remounting filesystem read-only

Complete dmesg and kconfig attached.  The lockup was running the same
kernel and X with a kernel "make -j4" on sda1 and a "dd if=/dev/zero
bs=1M of=/dev/sdb1" to a USB thumb drive running simultaneously; I'd
Ctrl-C'ed the dd about 30 seconds before the machine locked up (and the
dd was still in "D" so I'd attached an strace to it to see if anything
interesting would happen when it finally came back).

I haven't rebooted or remounted RW yet, happy to run whatever debug
commands would be useful.

Two issues here:

1. the lockup sucks, but I have no idea what to do about it.  There's
nothing useful in the logs and it wasn't responding to SysRq and the
keyboard LEDs weren't blinking.

2. after a lockup the journal recovery should not fail.

-andy

View attachment "config" of type "text/plain" (75458 bytes)

View attachment "dmesg" of type "text/plain" (54304 bytes)