From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: damien.lemoal@wdc.com
Cc: linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>,
Bart Van Assche <Bart.VanAssche@sandisk.com>
Subject: Re: [PATCH v2] sd: Write lock zone for REQ_OP_WRITE_ZEROES
Date: Thu, 11 May 2017 23:12:35 -0400 [thread overview]
Message-ID: <yq1fugaix98.fsf@oracle.com> (raw)
In-Reply-To: <20170508064819.12414-1-damien.lemoal@wdc.com> (damien lemoal's message of "Mon, 8 May 2017 15:48:19 +0900")
Damien,
> For a zoned block device, sd_zbc_complete() handles zone write unlock
> on completion of a REQ_OP_WRITE_ZEROES command but the zone write
> locking is missing from sd_setup_write_zeroes_cmnd(). This patch fixes
> this problem by locking the target zone of a REQ_OP_WRITE_ZEROES
> request.
Applied to 4.12/scsi-fixes. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2017-05-12 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 6:48 [PATCH v2] sd: Write lock zone for REQ_OP_WRITE_ZEROES damien.lemoal
2017-05-12 3:12 ` Martin K. Petersen [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=yq1fugaix98.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Bart.VanAssche@sandisk.com \
--cc=damien.lemoal@wdc.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox