From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: "axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"selvakuma.s1@samsung.com" <selvakuma.s1@samsung.com>,
"nj.shetty@samsung.com" <nj.shetty@samsung.com>,
"javier.gonz@samsung.com" <javier.gonz@samsung.com>,
Kanchan Joshi <joshi.k@samsung.com>
Subject: Re: [PATCH v2 1/1] null_blk: synchronization fix for zoned device
Date: Wed, 28 Oct 2020 01:45:10 +0000 [thread overview]
Message-ID: <DM6PR04MB652715459ACA71EBA758A1DDE7170@DM6PR04MB6527.namprd04.prod.outlook.com> (raw)
In-Reply-To: CY4PR04MB37511C151D0F37DC62BB4CE6E7350@CY4PR04MB3751.namprd04.prod.outlook.com
On 2020/09/28 19:12, Damien Le Moal wrote:
> On 2020/09/28 18:59, Kanchan Joshi wrote:
>> Parallel write,read,zone-mgmt operations accessing/altering zone state
>> and write-pointer may get into race. Avoid the situation by using a new
>> spinlock for zoned device.
>> Concurrent zone-appends (on a zone) returning same write-pointer issue
>> is also avoided using this lock.
>>
>> Fixes: e0489ed5daeb ("null_blk: Support REQ_OP_ZONE_APPEND")
>> Signed-off-by: Kanchan Joshi <joshi.k@samsung.com>
>> ---
>> drivers/block/null_blk.h | 1 +
>> drivers/block/null_blk_zoned.c | 22 ++++++++++++++++++----
>> 2 files changed, 19 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/block/null_blk.h b/drivers/block/null_blk.h
>> index daed4a9c3436..28099be50395 100644
>> --- a/drivers/block/null_blk.h
>> +++ b/drivers/block/null_blk.h
>> @@ -44,6 +44,7 @@ struct nullb_device {
>> unsigned int nr_zones;
>> struct blk_zone *zones;
>> sector_t zone_size_sects;
>> + spinlock_t zone_lock;
>>
>> unsigned long size; /* device size in MB */
>> unsigned long completion_nsec; /* time in ns to complete a request */
>> diff --git a/drivers/block/null_blk_zoned.c b/drivers/block/null_blk_zoned.c
>> index 3d25c9ad2383..e8d8b13aaa5a 100644
>> --- a/drivers/block/null_blk_zoned.c
>> +++ b/drivers/block/null_blk_zoned.c
>> @@ -45,6 +45,7 @@ int null_init_zoned_dev(struct nullb_device *dev, struct request_queue *q)
>> if (!dev->zones)
>> return -ENOMEM;
>>
>> + spin_lock_init(&dev->zone_lock);
>> if (dev->zone_nr_conv >= dev->nr_zones) {
>> dev->zone_nr_conv = dev->nr_zones - 1;
>> pr_info("changed the number of conventional zones to %u",
>> @@ -131,8 +132,11 @@ int null_report_zones(struct gendisk *disk, sector_t sector,
>> * So use a local copy to avoid corruption of the device zone
>> * array.
>> */
>> + spin_lock_irq(&dev->zone_lock);
>> memcpy(&zone, &dev->zones[first_zone + i],
>> sizeof(struct blk_zone));
>> + spin_unlock_irq(&dev->zone_lock);
>> +
>> error = cb(&zone, i, data);
>> if (error)
>> return error;
>> @@ -277,18 +281,28 @@ static blk_status_t null_zone_mgmt(struct nullb_cmd *cmd, enum req_opf op,
>> blk_status_t null_process_zoned_cmd(struct nullb_cmd *cmd, enum req_opf op,
>> sector_t sector, sector_t nr_sectors)
>> {
>> + blk_status_t sts;
>> + struct nullb_device *dev = cmd->nq->dev;
>> +
>> + spin_lock_irq(&dev->zone_lock);
>> switch (op) {
>> case REQ_OP_WRITE:
>> - return null_zone_write(cmd, sector, nr_sectors, false);
>> + sts = null_zone_write(cmd, sector, nr_sectors, false);
>> + break;
>> case REQ_OP_ZONE_APPEND:
>> - return null_zone_write(cmd, sector, nr_sectors, true);
>> + sts = null_zone_write(cmd, sector, nr_sectors, true);
>> + break;
>> case REQ_OP_ZONE_RESET:
>> case REQ_OP_ZONE_RESET_ALL:
>> case REQ_OP_ZONE_OPEN:
>> case REQ_OP_ZONE_CLOSE:
>> case REQ_OP_ZONE_FINISH:
>> - return null_zone_mgmt(cmd, op, sector);
>> + sts = null_zone_mgmt(cmd, op, sector);
>> + break;
>> default:
>> - return null_process_cmd(cmd, op, sector, nr_sectors);
>> + sts = null_process_cmd(cmd, op, sector, nr_sectors);
>> }
>> + spin_unlock_irq(&dev->zone_lock);
>> +
>> + return sts;
>> }
>>
>
> Looks good.
>
> Reviewed-by: Damien Le Moal <damien.lemoal@wdc.com>
Jens,
Could you queue this patch for rc2 please ?
We are seeing some issues with zone append in btrfs testing without it.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2020-10-28 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200928095910epcas5p2226ab95a8e4fbd3cfe3f48afb1a58c40@epcas5p2.samsung.com>
2020-09-28 9:55 ` [PATCH v2 0/1] concurrency handling for zoned null-blk Kanchan Joshi
[not found] ` <CGME20200928095914epcas5p1beae8d5a201c35b598fde8288532d58d@epcas5p1.samsung.com>
2020-09-28 9:55 ` [PATCH v2 1/1] null_blk: synchronization fix for zoned device Kanchan Joshi
2020-09-28 10:11 ` Damien Le Moal
2020-10-28 1:45 ` Damien Le Moal [this message]
2020-10-28 2:40 ` Jens Axboe
2020-09-28 10:08 ` [PATCH v2 0/1] concurrency handling for zoned null-blk Damien Le Moal
2020-09-28 12:11 ` Greg KH
2020-09-28 17:46 ` Kanchan Joshi
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=DM6PR04MB652715459ACA71EBA758A1DDE7170@DM6PR04MB6527.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=javier.gonz@samsung.com \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=nj.shetty@samsung.com \
--cc=selvakuma.s1@samsung.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).