From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: valdis.kletnieks@vt.edu
Cc: Andreas Dilger <adilger.kernel@dilger.ca>,
Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: [BUG] ext4 null pointer crash in linux-next
Date: Mon, 8 Oct 2018 22:22:43 -0400 [thread overview]
Message-ID: <20181009022243.GD3369@thunk.org> (raw)
In-Reply-To: <36243.1539028475@turing-police.cc.vt.edu>
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
next prev parent reply other threads:[~2018-10-09 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 19:54 [BUG] ext4 null pointer crash in linux-next valdis.kletnieks
2018-10-09 2:22 ` Theodore Y. Ts'o [this message]
2018-10-09 3:41 ` Bart Van Assche
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=20181009022243.GD3369@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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).