From: Bart Van Assche <bvanassche@acm.org>
To: Yi Zhang <yi.zhang@redhat.com>, linux-block@vger.kernel.org
Subject: Re: regression: block/001 lead kernel NULL pointer from v5.3-rc1
Date: Mon, 22 Jul 2019 15:36:32 -0700 [thread overview]
Message-ID: <2ef64389-39e0-455e-d972-0fcb72f76b54@acm.org> (raw)
In-Reply-To: <1106410976.2184883.1563817165884.JavaMail.zimbra@redhat.com>
On 7/22/19 10:39 AM, Yi Zhang wrote:
> With step[1], this kernel NULL pointer[2] can be triggered every time from v5.3-rc1, let me know if you need more info, thanks.
Have you already tried patch "[PATCH] scsi: fix the dma_max_mapping_size
call" (https://marc.info/?l=linux-scsi&m=156378725427719)?
Bart.
next prev parent reply other threads:[~2019-07-22 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1008069208.2174989.1563813991726.JavaMail.zimbra@redhat.com>
2019-07-22 17:39 ` regression: block/001 lead kernel NULL pointer from v5.3-rc1 Yi Zhang
2019-07-22 22:36 ` Bart Van Assche [this message]
2019-07-23 1:34 ` Ming Lei
2019-07-23 2:16 ` Yi Zhang
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=2ef64389-39e0-455e-d972-0fcb72f76b54@acm.org \
--to=bvanassche@acm.org \
--cc=linux-block@vger.kernel.org \
--cc=yi.zhang@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;
as well as URLs for NNTP newsgroup(s).