All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, dm-devel@lists.linux.dev,
	Mike Snitzer <snitzer@kernel.org>,
	Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: [PATCH 0/4] Zone write plugging and DM zone fixes
Date: Fri, 31 May 2024 08:58:17 +0900	[thread overview]
Message-ID: <99352774-5be7-4e13-93cd-6368ac7ddabd@kernel.org> (raw)
In-Reply-To: <1599ad1c-4395-46eb-9b9b-7439850a8300@kernel.dk>

On 5/31/24 6:03 AM, Jens Axboe wrote:
> On 5/29/24 11:40 PM, Damien Le Moal wrote:
>> The first patch of this series fixes null_blk to avoid weird zone
>> configurations, namely, a zoned device with a last smaller zone with a
>> zone capacity smaller than the zone size. Related to this, the next 2
>> patches fix the handling by zone write plugging of zoned devices with a
>> last smaller zone. That was completely botched in the initial series.
>>
>> Finally, the last patch addresses a long standing issue with zoned
>> device-mapper devices: no zone resource limits (max open and max active
>> zones limits) are not exposed to the user. This patch fixes that,
>> allowing for the limits of the underlying target devices to be exposed
>> with a warning for setups that lead to unreliable limits.
> 
> Would be nice to get the dm part acked, but I guess I can queue up 1-3
> for now for 6.10?

Yes please.

Mike, Mikulas,

Could you please review patch 4 ? It is a long standing issue with DM but now
that zone write plugging fakes a smaller 128 max open zones limit for drives
with no limits, zonefs gets confused and tests fail. So it would be great to
get this patch in for 6.10 as a fix.
Thanks !

-- 
Damien Le Moal
Western Digital Research


  reply	other threads:[~2024-05-30 23:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30  5:40 [PATCH 0/4] Zone write plugging and DM zone fixes Damien Le Moal
2024-05-30  5:40 ` [PATCH 1/4] null_blk: Do not allow runt zone with zone capacity smaller then zone size Damien Le Moal
2024-05-30  7:37   ` Niklas Cassel
2024-05-30 20:34   ` Bart Van Assche
2024-06-01  5:25   ` Christoph Hellwig
2024-06-03  6:53   ` Hannes Reinecke
2024-05-30  5:40 ` [PATCH 2/4] block: Fix validation of zoned device with a runt zone Damien Le Moal
2024-05-30  7:37   ` Niklas Cassel
2024-05-30 20:37   ` Bart Van Assche
2024-06-01  5:26   ` Christoph Hellwig
2024-06-03  6:55   ` Hannes Reinecke
2024-05-30  5:40 ` [PATCH 3/4] block: Fix zone write plugging handling of devices " Damien Le Moal
2024-05-30  7:37   ` Niklas Cassel
2024-05-30 11:09     ` Damien Le Moal
2024-05-30 12:51   ` Niklas Cassel
2024-05-30 20:40   ` Bart Van Assche
2024-06-01  5:26   ` Christoph Hellwig
2024-06-03  6:56   ` Hannes Reinecke
2024-05-30  5:40 ` [PATCH 4/4] dm: Improve zone resource limits handling Damien Le Moal
2024-05-30  7:37   ` Niklas Cassel
2024-05-31 19:26   ` Benjamin Marzinski
2024-06-01  5:29     ` Christoph Hellwig
2024-06-01  5:33       ` Christoph Hellwig
2024-06-03  0:44         ` Damien Le Moal
2024-06-01  5:29   ` Christoph Hellwig
2024-06-03  6:58   ` Hannes Reinecke
2024-05-30 21:03 ` [PATCH 0/4] Zone write plugging and DM zone fixes Jens Axboe
2024-05-30 23:58   ` Damien Le Moal [this message]
2024-05-30 21:04 ` (subset) " 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=99352774-5be7-4e13-93cd-6368ac7ddabd@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=axboe@kernel.dk \
    --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.