From: Sagi Grimberg <sagi@grimberg.me>
To: Logan Gunthorpe <logang@deltatee.com>,
Keith Busch <kbusch@kernel.org>,
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Cc: hch@lst.de, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 1/2] nvmet: fix oops in nvmet_execute_passthru_cmd()
Date: Thu, 6 Aug 2020 12:18:13 -0700 [thread overview]
Message-ID: <2b345117-b149-939b-10e4-9493223c8f56@grimberg.me> (raw)
In-Reply-To: <1f6a1c73-fd0e-d05d-3254-03d0592ac998@deltatee.com>
> I don't think this is quite accurate either. It looks to me like it's
> just a bug in the error path logic. If the namespace is invalid, it
> doesn't even try to allocate the request so it should really just order
> the cleanup correctly and skip it, if it's not allocated.
>
> I think a fix like this would be cleaner:
Can you please send a proper patch for this Logan/Chaitanya?
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-08-06 19:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 7:31 [PATCH 0/2] nvmet: couple of passthru fixes Chaitanya Kulkarni
2020-08-06 7:31 ` [PATCH 1/2] nvmet: fix oops in nvmet_execute_passthru_cmd() Chaitanya Kulkarni
2020-08-06 15:42 ` Keith Busch
2020-08-06 16:12 ` Logan Gunthorpe
2020-08-06 16:26 ` Keith Busch
2020-08-06 19:40 ` Chaitanya Kulkarni
2020-08-06 19:45 ` Logan Gunthorpe
2020-08-06 19:54 ` Sagi Grimberg
2020-08-06 19:55 ` Logan Gunthorpe
2020-08-06 19:57 ` Chaitanya Kulkarni
2020-08-06 20:03 ` Sagi Grimberg
2020-08-06 20:06 ` Chaitanya Kulkarni
2020-08-06 19:55 ` Chaitanya Kulkarni
2020-08-06 19:18 ` Sagi Grimberg [this message]
2020-08-06 19:31 ` Chaitanya Kulkarni
2020-08-06 19:41 ` Sagi Grimberg
2020-08-06 19:44 ` Chaitanya Kulkarni
2020-08-06 19:29 ` Chaitanya Kulkarni
2020-08-06 7:31 ` [PATCH 2/2] nvmet: call blk_mq_free_request() directly Chaitanya Kulkarni
2020-08-06 15:45 ` Keith Busch
2020-08-06 16:14 ` Logan Gunthorpe
2020-08-06 19:19 ` Sagi Grimberg
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=2b345117-b149-939b-10e4-9493223c8f56@grimberg.me \
--to=sagi@grimberg.me \
--cc=chaitanya.kulkarni@wdc.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=logang@deltatee.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).