From: Bart Van Assche <bvanassche@acm.org>
To: valdis.kletnieks@vt.edu, Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jens Axboe <axboe@kernel.dk>
Cc: 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 20:41:15 -0700 [thread overview]
Message-ID: <839b29df-08af-403c-da3e-e1bc9eca1685@acm.org> (raw)
In-Reply-To: <36243.1539028475@turing-police.cc.vt.edu>
On 10/8/18 12:54 PM, valdis.kletnieks@vt.edu wrote:
> [ 680.692915] RIP: 0010:__get_request+0x31/0x7e0
Can you provide the source code line number that corresponds to that
address? If you haven't done this before: enter gdb
${path_to_kernel_source_tree}/vmlinux in a shell and then run "list
*(__get_request+0x31)" (without the double quotes).
Additionally, which block driver is being used in your setup under the
ext4 filesystem?
Thanks,
Bart.
prev parent reply other threads:[~2018-10-09 3:41 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
2018-10-09 3:41 ` Bart Van Assche [this message]
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=839b29df-08af-403c-da3e-e1bc9eca1685@acm.org \
--to=bvanassche@acm.org \
--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=tytso@mit.edu \
--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