linux-ext4 - Re: [BUG] ext4 null pointer crash in linux-next

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]

Message-ID: <20181009022243.GD3369@thunk.org>
Date:   Mon, 8 Oct 2018 22:22:43 -0400
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     valdis.kletnieks@...edu
Cc:     Andreas Dilger <adilger.kernel@...ger.ca>,
        Jens Axboe <axboe@...nel.dk>, linux-kernel@...r.kernel.org,
        linux-ext4@...r.kernel.org, linux-block@...r.kernel.org
Subject: Re: [BUG] ext4 null pointer crash in linux-next

On Mon, Oct 08, 2018 at 03:54:35PM -0400, valdis.kletnieks@...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