mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Daniel Wagner <dwagner@suse.de>, linux-nvme@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
	Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@fb.com>,
	Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] nvme-tcp: Check if request has started before processing it
Date: Sat, 13 Feb 2021 09:42:46 +0100	[thread overview]
Message-ID: <3f183393-cc1e-3d03-3074-40c18f3cb9cc@suse.de> (raw)
In-Reply-To: <20210212181738.79274-1-dwagner@suse.de>

On 2/12/21 7:17 PM, Daniel Wagner wrote:
> blk_mq_tag_to_rq() will always return a request if the command_id is
> in the valid range. Check if the request has been started. If we
> blindly process the request we might double complete a request which
> can be fatal.
> 
> Signed-off-by: Daniel Wagner <dwagner@suse.de>
> ---
> 
> This patch is against nvme-5.12.
> 
> There is one blk_mq_tag_to_rq() in nvme_tcp_recv_ddgst() which I
> didn't update as I am not sure if it's also needed.
> 
I guess it is; this patch is essentially a protection against invalid 
frames, and as such affects all places.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                Kernel Storage Architect
hare@suse.de                              +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer

      parent reply	other threads:[~2021-02-13  8:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 18:17 Daniel Wagner
2021-02-12 20:58 ` Sagi Grimberg
2021-02-12 21:09   ` Keith Busch
2021-02-12 21:49     ` Sagi Grimberg
2021-02-13  8:46       ` Hannes Reinecke
2021-02-15 10:40         ` Daniel Wagner
2021-02-15 21:29           ` Sagi Grimberg
2021-02-26 12:35             ` Daniel Wagner
2021-02-26 12:54               ` Hannes Reinecke
2021-02-26 16:13                 ` Keith Busch
2021-02-26 16:42                   ` Hannes Reinecke
2021-02-26 17:19                     ` Keith Busch
2021-03-01 13:26                       ` Daniel Wagner
2021-03-01 13:55                         ` Hannes Reinecke
2021-03-01 16:05                           ` Keith Busch
2021-03-01 16:53                             ` Hannes Reinecke
2021-03-01 20:59                               ` Keith Busch
2021-03-02  7:18                                 ` Hannes Reinecke
2021-03-02 18:45                                   ` Keith Busch
2021-02-15 21:23         ` Sagi Grimberg
2021-02-16  8:51           ` Hannes Reinecke
2021-02-13  8:42 ` Hannes Reinecke [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=3f183393-cc1e-3d03-3074-40c18f3cb9cc@suse.de \
    --to=hare@suse.de \
    --cc=axboe@fb.com \
    --cc=dwagner@suse.de \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --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

all inboxes | Powered by JetHome®