[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250701-muskatnuss-exklusiv-36750fede25f@brauner>
Date: Tue, 1 Jul 2025 13:56:17 +0200
From: Christian Brauner <brauner@...nel.org>
To: Pankaj Raghav <p.raghav@...sung.com>
Cc: Christian Brauner <brauner@...nel.org>,
linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org,
kernel@...kajraghav.com,
gost.dev@...sung.com,
Matthew Wilcox <willy@...radead.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
Jan Kara <jack@...e.cz>,
mcgrof@...nel.org
Subject: Re: [PATCH v4] fs/buffer: remove the min and max limit checks in __getblk_slow()
On Thu, 26 Jun 2025 13:32:23 +0200, Pankaj Raghav wrote:
> All filesystems will already check the max and min value of their block
> size during their initialization. __getblk_slow() is a very low-level
> function to have these checks. Remove them and only check for logical
> block size alignment.
>
> As this check with logical block size alignment might never trigger, add
> WARN_ON_ONCE() to the check. As WARN_ON_ONCE() will already print the
> stack, remove the call to dump_stack().
>
> [...]
Applied to the vfs-6.17.misc branch of the vfs/vfs.git tree.
Patches in the vfs-6.17.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.17.misc
[1/1] fs/buffer: remove the min and max limit checks in __getblk_slow()
https://git.kernel.org/vfs/vfs/c/36996c013faf
Powered by blists - more mailing lists