[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPjX3FfyQ4wDD54_=wz62OBsSO30C2f7dmXZcKEu2JgpuER_KQ@mail.gmail.com>
Date: Wed, 5 Nov 2025 19:40:16 +0100
From: Daniel Vacek <neelx@...e.com>
To: Christian Brauner <brauner@...nel.org>
Cc: linux-fsdevel@...r.kernel.org, Alexander Viro <viro@...iv.linux.org.uk>,
Jan Kara <jack@...e.cz>, linux-btrfs@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-xfs@...r.kernel.org
Subject: Re: [PATCH RFC 8/8] xfs: use super write guard in xfs_file_ioctl()
On Tue, 4 Nov 2025 at 13:17, Christian Brauner <brauner@...nel.org> wrote:
>
> Signed-off-by: Christian Brauner <brauner@...nel.org>
> ---
> fs/xfs/xfs_ioctl.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c
> index a6bb7ee7a27a..f72e96f54cb5 100644
> --- a/fs/xfs/xfs_ioctl.c
> +++ b/fs/xfs/xfs_ioctl.c
> @@ -1408,10 +1408,8 @@ xfs_file_ioctl(
>
> trace_xfs_ioc_free_eofblocks(mp, &icw, _RET_IP_);
>
> - sb_start_write(mp->m_super);
> - error = xfs_blockgc_free_space(mp, &icw);
> - sb_end_write(mp->m_super);
> - return error;
> + scoped_guard(super_write, mp->m_super)
> + return xfs_blockgc_free_space(mp, &icw);
Again, scope_guard where not needed, right?
--nX
> }
>
> case XFS_IOC_EXCHANGE_RANGE:
>
> --
> 2.47.3
>
>
Powered by blists - more mailing lists