[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d7004ae9-ad68-cb61-9ca8-0bf61efa0c21@acm.org>
Date: Wed, 28 Sep 2022 11:13:28 -0700
From: Bart Van Assche <bvanassche@....org>
To: Pankaj Raghav <p.raghav@...sung.com>, snitzer@...nel.org,
axboe@...nel.dk, agk@...hat.com, hch@....de,
damien.lemoal@...nsource.wdc.com
Cc: jaegeuk@...nel.org, gost.dev@...sung.com,
linux-kernel@...r.kernel.org, hare@...e.de,
matias.bjorling@....com, Johannes.Thumshirn@....com,
linux-block@...r.kernel.org, linux-nvme@...ts.infradead.org,
pankydev8@...il.com, dm-devel@...hat.com
Subject: Re: [PATCH v15 11/13] dm: call dm_zone_endio after the target endio
callback for zoned devices
On 9/23/22 10:36, Pankaj Raghav wrote:
> dm_zone_endio() updates the bi_sector of orig bio for zoned devices that
> uses either native append or append emulation, and it is called before the
> endio of the target. But target endio can still update the clone bio
> after dm_zone_endio is called, thereby, the orig bio does not contain
> the updated information anymore.
>
> Currently, this is not a problem as the targets that support zoned devices
> such as dm-zoned, dm-linear, and dm-crypt do not have an endio function,
> and even if they do (such as dm-flakey), they don't modify the
> bio->bi_iter.bi_sector of the cloned bio that is used to update the
> orig_bio's bi_sector in dm_zone_endio function.
>
> This is a prep patch for the new dm-po2zoned target as it modifies
> bi_sector in the endio callback.
>
> Call dm_zone_endio for zoned devices after calling the target's endio
> function.
Reviewed-by: Bart Van Assche <bvanassche@....org>
Powered by blists - more mailing lists