Re: [PATCH 1/4] block: consecutive blk_status_t error codes
Christoph Hellwig <[email protected]> Thu, 5 Mar 2026 06:12:49 -0800
| Newsgroups | org.kernel.vger.linux-bcache,dev.linux.lists.dm-devel,dev.linux.lists.drbd-dev,net.sourceforge.lists.linux-f2fs-devel,org.kernel.vger.linux-block,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Mar 04, 2026 at 08:04:06PM +0100, Andreas Gruenbacher wrote:
> Since commit 9da3d1e912f3 ("block: Add core atomic write support"),
> there is a gap in the blk_status_t codes and block status code 18 is
> unused. This causes blk_status_to_errno() and blk_status_to_str() to
> return incorrect values for that code. Make the blk_status_t codes
> consecutive again to avoid that.
Looks good:
Reviewed-by: Christoph Hellwig <[email protected]>