From: Patrick Steinhardt <ps@pks.im>
To: Bart Van Assche <Bart.VanAssche@wdc.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"ming.lei@redhat.com" <ming.lei@redhat.com>
Subject: Re: [PATCH] block: fix NPE when resuming SCSI devices using blk-mq
Date: Sat, 28 Jul 2018 20:50:49 +0200 [thread overview]
Message-ID: <20180728185049.GA1663@xps.pks.im> (raw)
In-Reply-To: <6f00aeea242c20be1e2709bb00d27d79a8a8facf.camel@wdc.com>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
On Fri, Jul 27, 2018 at 03:03:09PM +0000, Bart Van Assche wrote:
> On Fri, 2018-07-27 at 14:35 +-0200, Patrick Steinhardt wrote:
> +AD4- +ADw-1+AD4AWw- 53.411700+AF0- BUG: unable to handle kernel NULL pointer dereference at 00000000000001a8
> +AD4- +ADw-4+AD4AWw- 53.411733+AF0- RIP: 0010:blk+AF8-set+AF8-runtime+AF8-active+-0x2d/0x50
>
> Are you sure commit 4fd41a8552af (+ACI-SCSI: Fix NULL pointer dereference in
> runtime PM+ACIAOw- December 2015) is in your kernel tree?
>
> Bart.
Yes, I am:
$ git describe
v4.17.10
$ git tag --contains 4fd41a8552af v4.17.10
v4.17.10
I've also manually verified that all changes from 4fd41a8552af
are contained in the sources, which they are.
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-07-28 18:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 13:29 [PATCH] block: fix NPE when resuming SCSI devices using blk-mq Patrick Steinhardt
2018-07-13 13:41 ` Ming Lei
2018-07-16 15:11 ` Patrick Steinhardt
2018-07-29 9:41 ` Tomas Janousek
2018-07-30 7:59 ` Patrick Steinhardt
2018-07-30 11:50 ` Ming Lei
2018-07-30 15:00 ` Tomas Janousek
2018-07-25 18:13 ` Bart Van Assche
2018-07-26 8:38 ` Patrick Steinhardt
2018-07-26 13:51 ` Bart Van Assche
2018-07-27 12:35 ` Patrick Steinhardt
2018-07-27 15:03 ` Bart Van Assche
2018-07-28 18:50 ` Patrick Steinhardt [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=20180728185049.GA1663@xps.pks.im \
--to=ps@pks.im \
--cc=Bart.VanAssche@wdc.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
/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