All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>,
	linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
	dm-devel@lists.linux.dev, Mike Snitzer <snitzer@kernel.org>,
	Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: [PATCH v3 3/5] dm: Always split write BIOs to zoned device limits
Date: Thu, 26 Jun 2025 08:41:22 +0900	[thread overview]
Message-ID: <4f4408fd-c87c-4982-bad1-87798add9516@kernel.org> (raw)
In-Reply-To: <654fed1e-ce53-4386-a966-97c50931e9b5@acm.org>

On 6/26/25 01:34, Bart Van Assche wrote:
> On 6/25/25 2:33 AM, Damien Le Moal wrote:
>> +	/*
>> +	 * Mapped devices that require zone append emulation will use the block
>> +	 * layer zone write plugging. In such case, we must split any large BIO
>> +	 * to the mapped device limits to avoid potential deadlocks with queue
>> +	 * freeze operations.
>> +	 */
>> +	if (!dm_emulate_zone_append(md))
>> +		return false;
>> +	return bio_needs_zone_write_plugging(bio) || bio_straddles_zones(bio);
> 
> Changing the dm_emulate_zone_append() call into a
> disk_need_zone_resources() call or a disk->zone_wplugs_hash test
> probably would make the intention of the if-statement more clear.

The comment is not clear enough ?

> Additionally, bio_needs_zone_write_plugging() already tests
> disk->zone_wplugs_hash. Isn't the dm_emulate_zone_append() call
> superfluous because of this?

Yes, I think it is. But I did try to minimize changes given that this is a fix
which is not small already...

I will do more testing and send follow-up cleanup patches.

-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2025-06-25 23:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25  9:33 [PATCH v3 0/5] Fix write operation handling for zoned DM devices Damien Le Moal
2025-06-25  9:33 ` [PATCH v3 1/5] block: Make REQ_OP_ZONE_FINISH a write operation Damien Le Moal
2025-06-25 11:28   ` Christoph Hellwig
2025-06-25 11:42   ` Johannes Thumshirn
2025-06-25 15:44   ` Bart Van Assche
2025-06-25 16:29   ` Bart Van Assche
2025-06-25 23:36     ` Damien Le Moal
2025-06-26 20:29       ` Bart Van Assche
2025-06-25  9:33 ` [PATCH v3 2/5] block: Introduce bio_needs_zone_write_plugging() Damien Le Moal
2025-06-25 11:28   ` Christoph Hellwig
2025-06-25 11:47   ` Johannes Thumshirn
2025-06-25 15:48   ` Bart Van Assche
2025-06-25 23:38     ` Damien Le Moal
2025-06-26 16:37       ` Bart Van Assche
2025-06-25  9:33 ` [PATCH v3 3/5] dm: Always split write BIOs to zoned device limits Damien Le Moal
2025-06-25 11:49   ` Johannes Thumshirn
2025-06-25 16:30   ` Mikulas Patocka
2025-06-25 16:34   ` Bart Van Assche
2025-06-25 23:41     ` Damien Le Moal [this message]
2025-06-25  9:33 ` [PATCH v3 4/5] dm: dm-crypt: Do not partially accept write BIOs with zoned targets Damien Le Moal
2025-06-25 16:31   ` Mikulas Patocka
2025-06-25 16:42   ` Bart Van Assche
2025-06-25  9:33 ` [PATCH v3 5/5] dm: Check for forbidden splitting of zone write operations Damien Le Moal
2025-06-25 16:31   ` Mikulas Patocka
2025-06-25 16:37 ` [PATCH v3 0/5] Fix write operation handling for zoned DM devices Jens Axboe

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=4f4408fd-c87c-4982-bad1-87798add9516@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=dm-devel@lists.linux.dev \
    --cc=linux-block@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=snitzer@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 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.