public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Damien Le Moal <Damien.LeMoal@wdc.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH] sd_zbc: Write unlock zone from sd_uninit_cmnd()
Date: Tue, 8 Aug 2017 15:07:50 +0000	[thread overview]
Message-ID: <1502204867.2250.1.camel@wdc.com> (raw)
In-Reply-To: <20170808041746.31341-1-damien.lemoal@wdc.com>

On Tue, 2017-08-08 at 13:17 +0900, Damien Le Moal wrote:
> Releasing the write lock of a zone when the write commnand that
                                                    ^^^^^^^^
                                                    command?
> acquired the lock completes can cause deadlocks with scsi-mq due to
> potential queue reordering if the lock owning request is requeued and
> not executed.

Please note that even with scsi-sq requeueing can cause request reordering.

> Since sd_uninit_cmnd() is always called when a request is requeued,
> call sd_zbc_write_unlock_zone() from that function for write requests
> that acquired a zone lock. Acquisition of a zone lock by a write command
> is indicated using the new command flag SCMD_ZONE_WRITE_LOCK.

Hello Damien,

Since this patch differs slightly from the version that was posted a few
days ago, should a "v2" label have been added to the subject and should a
changelog have been included? Anyway:

Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com>


  reply	other threads:[~2017-08-08 15:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08  4:17 [PATCH] sd_zbc: Write unlock zone from sd_uninit_cmnd() Damien Le Moal
2017-08-08 15:07 ` Bart Van Assche [this message]
2017-08-09  2:19   ` Damien Le Moal
2017-08-09  2:47     ` Damien Le Moal
2017-08-09  3:57       ` Bart Van Assche
2017-08-09  4:07         ` Damien Le Moal
2017-08-09  4:15           ` Bart Van Assche
2017-08-09  5:15             ` Damien Le Moal
2017-08-09 15:24               ` Bart Van Assche
2017-08-10  2:14                 ` Damien Le Moal
2017-08-10  3:09                   ` Damien Le Moal
2017-08-10 15:35                   ` Bart Van Assche

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=1502204867.2250.1.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=Damien.LeMoal@wdc.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox