Re: [BUG] ext4 null pointer crash in linux-next
From: "Theodore Y. Ts'o" <tytso@mit.edu>
Date: 2018-10-09 02:22:47
Also in:
linux-ext4, lkml
From: "Theodore Y. Ts'o" <tytso@mit.edu>
Date: 2018-10-09 02:22:47
Also in:
linux-ext4, lkml
On Mon, Oct 08, 2018 at 03:54:35PM -0400, valdis.kletnieks@vt.edu wrote:
I'm seeing a fairly replicable crash/hang with a traceback implicating ext4 (or possibly the block layer). next-20180918 seemed stable, but next-20180926 and -next-20181005 have a habit of crashing while dnf is updating software (so far, I've hit it 6 times with identical tracebacks while attempting to update software This ringing any bells, or did I just buy myself another git bisect? Google says that ext4_mpage_readpages from the traceback hasn't been referenced in the last 2 months...
I'm afraid you're going to have to do a git bisect. I've been doing full regression tests of ext4.git and nothing like this has turned up. Instead of doing a full bisect, maybe try doing the ext4.git tree by itself, and the block.git tree by itself, and maybe those two trees merged together? - Ted