From: hch <hch@lst.de>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: John Garry <john.g.garry@oracle.com>,
"axboe@kernel.dk" <axboe@kernel.dk>, hch <hch@lst.de>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"kbusch@kernel.org" <kbusch@kernel.org>,
Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: [PATCH v2 1/2] block: Read max write zeroes once for __blkdev_issue_write_zeroes()
Date: Wed, 28 Aug 2024 09:17:29 +0200 [thread overview]
Message-ID: <20240828071729.GA1653@lst.de> (raw)
In-Reply-To: <jxozlplk5fforzhc5hgmanqszw7pb7kuxbo2f23e5xtu3yozdy@tneiyvantisq>
On Wed, Aug 28, 2024 at 07:15:55AM +0000, Shinichiro Kawasaki wrote:
> I ran may test set for the kernel v6.11-rc5 and found that this commit triggers
> an error. When I set up xfs with a dm-zoned device on a TCMU zoned device and
> filled the filesystem, the kernel reported this error message:
>
> device-mapper: zoned reclaim: (sdg): Align zone 19 wp 0 to 32736 (wp+32736) blocks failed -121
>
> When dm-zoned calls blkdev_issue_zeorout(), EREMOTEIO 121 was returned, then
> the error was reported. I think a change in this commit is the cause. Please
> find my comment below.
This patch should fix it:
https://lore.kernel.org/linux-block/20240827175340.GB1977952@frogsfrogsfrogs/
next prev parent reply other threads:[~2024-08-28 7:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 16:32 [PATCH v2 0/2] block: Fix __blkdev_issue_write_zeroes() limit handling John Garry
2024-08-15 16:32 ` [PATCH v2 1/2] block: Read max write zeroes once for __blkdev_issue_write_zeroes() John Garry
2024-08-15 17:43 ` Martin K. Petersen
2024-08-16 18:34 ` Nitesh Shetty
2024-08-17 15:33 ` John Garry
2024-08-19 15:15 ` Nitesh Shetty
2024-08-28 7:15 ` Shinichiro Kawasaki
2024-08-28 7:17 ` hch [this message]
2024-08-28 7:25 ` Shinichiro Kawasaki
2024-08-15 16:32 ` [PATCH v2 2/2] block: Drop NULL check in bdev_write_zeroes_sectors() John Garry
2024-08-15 17:43 ` Martin K. Petersen
2024-08-19 15:16 ` Nitesh Shetty
2024-08-19 15:49 ` [PATCH v2 0/2] block: Fix __blkdev_issue_write_zeroes() limit handling 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=20240828071729.GA1653@lst.de \
--to=hch@lst.de \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=john.g.garry@oracle.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=shinichiro.kawasaki@wdc.com \
/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.