All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Keith Busch <kbusch@kernel.org>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"hch@lst.de" <hch@lst.de>,
	"alan.adamson@oracle.com" <alan.adamson@oracle.com>,
	Chaitanya Kulkarni <chaitanyak@nvidia.com>
Subject: Re: [PATCH] nvme-core: mark passthru requests RQF_QUIET flag
Date: Wed, 6 Apr 2022 17:01:46 +0000	[thread overview]
Message-ID: <21a3a237-5f3b-a608-2d79-e0a5fdcc0d88@nvidia.com> (raw)
In-Reply-To: <Yk3FT78uVW+9rRV5@kbusch-mbp.dhcp.thefacebook.com>

On 4/6/22 09:52, Keith Busch wrote:
> On Wed, Apr 06, 2022 at 09:41:09AM -0700, Chaitanya Kulkarni wrote:
>> @@ -370,7 +370,8 @@ static inline void nvme_end_req(struct request *req)
>>   {
>>   	blk_status_t status = nvme_error_status(nvme_req(req)->status);
>>   
>> -	if (unlikely(nvme_req(req)->status != NVME_SC_SUCCESS))
>> +	if (unlikely(nvme_req(req)->status != NVME_SC_SUCCESS &&
>> +		    !(req->rq_flags & RQF_QUIET)))
>>   		nvme_log_error(req);
>>   	nvme_end_req_zoned(req);
>>   	nvme_trace_bio_complete(req);
>> @@ -651,6 +652,7 @@ void nvme_init_request(struct request *req, struct nvme_command *cmd)
>>   	cmd->common.flags &= ~NVME_CMD_SGL_ALL;
>>   
>>   	req->cmd_flags |= REQ_FAILFAST_DRIVER;
>> +	req->rq_flags |= RQF_QUIET;
> 
> This defeats the admin error logging logic since every admin command comes
> through here. If you're sure we should do this, then I suppose you can remove
> that unreachable code.

If you point out the unreachable code that will be great,
I'll keep looking meanwhile...

-ck


  reply	other threads:[~2022-04-06 17:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 16:41 [PATCH] nvme-core: mark passthru requests RQF_QUIET flag Chaitanya Kulkarni
2022-04-06 16:52 ` Keith Busch
2022-04-06 17:01   ` Chaitanya Kulkarni [this message]
2022-04-06 17:21     ` Keith Busch
2022-04-06 22:06       ` Alan Adamson
2022-04-06 22:16         ` Chaitanya Kulkarni
2022-04-06 23:29           ` Alan Adamson
2022-04-07 19:40             ` Chaitanya Kulkarni
2022-04-07  8:48           ` Christoph Hellwig
2022-04-07  8:51         ` hch
2022-04-07 11:52           ` Sagi Grimberg
2022-04-07 20:10             ` Chaitanya Kulkarni
2022-04-07 20:35               ` Alan Adamson
2022-04-07 21:00                 ` Chaitanya Kulkarni
2022-04-07 21:13                   ` Alan Adamson
2022-04-08  2:13                     ` Chaitanya Kulkarni
2022-04-08 16:24                       ` Alan Adamson
2022-04-09  0:10                         ` Chaitanya Kulkarni
2022-04-11 18:31                           ` Alan Adamson
2022-04-11 19:53                             ` Chaitanya Kulkarni
2022-04-11 21:39                               ` Alan Adamson
2022-04-07 16:15           ` Alan Adamson
2022-04-06 17:03   ` 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=21a3a237-5f3b-a608-2d79-e0a5fdcc0d88@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=alan.adamson@oracle.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.