All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Christoph Hellwig <hch@lst.de>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH v4 0/3] blk-mq: Fix a race between iterating over requests and freeing requests
Date: Tue, 30 Mar 2021 15:30:02 -0700	[thread overview]
Message-ID: <deedbe3f-0236-26fe-97ef-000c317687d8@acm.org> (raw)
In-Reply-To: <20210329020028.18241-1-bvanassche@acm.org>

On 3/28/21 7:00 PM, Bart Van Assche wrote:
> This patch series fixes the race between iterating over requests and
> freeing requests that has been reported by multiple different users over
> the past two years. Please consider this patch series for kernel v5.13.

Hi Christoph and Martin,

Since this patch series makes significant changes in the NVMe core and 
also in the SCSI core, your feedback would be appreciated.

Thanks,

Bart.

  parent reply	other threads:[~2021-03-30 22:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29  2:00 [PATCH v4 0/3] blk-mq: Fix a race between iterating over requests and freeing requests Bart Van Assche
2021-03-29  2:00 ` [PATCH v4 1/3] blk-mq: Move the elevator_exit() definition Bart Van Assche
2021-03-29  2:00 ` [PATCH v4 2/3] blk-mq: Introduce atomic variants of the tag iteration functions Bart Van Assche
2021-03-29  2:00 ` [PATCH v4 3/3] blk-mq: Fix a race between iterating over requests and freeing requests Bart Van Assche
2021-04-02 23:59   ` Khazhy Kumykov
2021-04-03  3:25     ` Bart Van Assche
2021-04-03  3:37       ` Khazhy Kumykov
2021-04-04  1:11         ` Bart Van Assche
2021-03-30 22:30 ` Bart Van Assche [this message]
2021-04-01  0:48 ` [PATCH v4 0/3] " Shinichiro Kawasaki
2021-04-01  1:55 ` Martin K. Petersen
2021-04-02 10:00 ` Christoph Hellwig

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=deedbe3f-0236-26fe-97ef-000c317687d8@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=martin.petersen@oracle.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 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.