From: Yi Zhang <yi.zhang@redhat.com>
To: linux-nvme@lists.infradead.org,
linux-block <linux-block@vger.kernel.org>
Cc: axboe@kernel.dk, Rachel Sibley <rasibley@redhat.com>,
Sagi Grimberg <sagi@grimberg.me>,
CKI Project <cki-project@redhat.com>
Subject: Re: kernel null pointer at nvme_tcp_init_iter[nvme_tcp] with blktests nvme-tcp/012
Date: Sun, 7 Feb 2021 12:50:01 +0800 [thread overview]
Message-ID: <80b7184e-cdfb-cebc-fe07-a228ce57a9e7@redhat.com> (raw)
In-Reply-To: <630237787.11660686.1612580898410.JavaMail.zimbra@redhat.com>
The issue was introduced after merge the NVMe updates
commit 0fd6456fd1f4c8f3ec5a2df6ed7f34458a180409 (HEAD)
Merge: 44d10e4b2f2c 0d7389718c32
Author: Jens Axboe <axboe@kernel.dk>
Date: Tue Feb 2 07:12:06 2021 -0700
Merge branch 'for-5.12/drivers' into for-next
* for-5.12/drivers: (22 commits)
nvme-tcp: use cancel tagset helper for tear down
nvme-rdma: use cancel tagset helper for tear down
nvme-tcp: add clean action for failed reconnection
nvme-rdma: add clean action for failed reconnection
nvme-core: add cancel tagset helpers
nvme-core: get rid of the extra space
nvme: add tracing of zns commands
nvme: parse format nvm command details when tracing
nvme: update enumerations for status codes
nvmet: add lba to sect conversion helpers
nvmet: remove extra variable in identify ns
nvmet: remove extra variable in id-desclist
nvmet: remove extra variable in smart log nsid
nvme: refactor ns->ctrl by request
nvme-tcp: pass multipage bvec to request iov_iter
nvme-tcp: get rid of unused helper function
nvme-tcp: fix wrong setting of request iov_iter
nvme: support command retry delay for admin command
nvme: constify static attribute_group structs
nvmet-fc: use RCU proctection for assoc_list
On 2/6/21 11:08 AM, Yi Zhang wrote:
> blktests nvme-tcp/012
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next parent reply other threads:[~2021-02-07 4:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cki.F3E139361A.EN5MUSJKK9@redhat.com>
[not found] ` <630237787.11660686.1612580898410.JavaMail.zimbra@redhat.com>
2021-02-07 4:50 ` Yi Zhang [this message]
2021-02-07 5:25 ` kernel null pointer at nvme_tcp_init_iter[nvme_tcp] with blktests nvme-tcp/012 Chaitanya Kulkarni
2021-02-08 6:48 ` Yi Zhang
2021-02-07 5:48 ` Chaitanya Kulkarni
2021-02-07 5:58 ` Chaitanya Kulkarni
2021-02-07 7:14 ` kernel null pointer at nvme_tcp_init_iter+0x7d/0xd0 [nvme_tcp] Chaitanya Kulkarni
2021-02-08 9:53 ` Sagi Grimberg
2021-02-08 9:46 ` Sagi Grimberg
2021-02-08 13:28 ` Yi Zhang
2021-02-08 17:54 ` Sagi Grimberg
2021-02-08 18:42 ` Sagi Grimberg
2021-02-09 4:21 ` Ming Lei
2021-02-09 7:21 ` Sagi Grimberg
2021-02-09 7:50 ` Ming Lei
2021-02-09 8:34 ` Chaitanya Kulkarni
2021-02-09 10:09 ` Sagi Grimberg
2021-02-09 10:07 ` Sagi Grimberg
2021-02-09 10:33 ` Ming Lei
2021-02-09 10:36 ` Sagi Grimberg
2021-02-09 10:25 ` Sagi Grimberg
2021-02-09 12:57 ` Yi Zhang
2021-02-09 18:01 ` Sagi Grimberg
2021-02-10 2:51 ` Yi Zhang
2021-02-10 3:38 ` Keith Busch
2021-02-10 5:03 ` Chaitanya Kulkarni
2021-02-10 22:06 ` Sagi Grimberg
2021-02-10 22:15 ` Chaitanya Kulkarni
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=80b7184e-cdfb-cebc-fe07-a228ce57a9e7@redhat.com \
--to=yi.zhang@redhat.com \
--cc=axboe@kernel.dk \
--cc=cki-project@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=rasibley@redhat.com \
--cc=sagi@grimberg.me \
/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