From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Chandan Babu R <chandan.babu@oracle.com>,
Brian Foster <bfoster@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Jan Kara <jack@suse.cz>, Theodore Ts'o <tytso@mit.edu>,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/6] fs: sort out the fallocate mode vs flag mess
Date: Tue, 27 Aug 2024 07:55:02 -0700 [thread overview]
Message-ID: <20240827145502.GP865349@frogsfrogsfrogs> (raw)
In-Reply-To: <20240827065123.1762168-4-hch@lst.de>
On Tue, Aug 27, 2024 at 08:50:47AM +0200, Christoph Hellwig wrote:
> The fallocate system call takes a mode argument, but that argument
> contains a wild mix of exclusive modes and an optional flags.
>
> Replace FALLOC_FL_SUPPORTED_MASK with FALLOC_FL_MODE_MASK, which excludes
> the optional flag bit, so that we can use switch statement on the value
> to easily enumerate the cases while getting the check for duplicate modes
> for free.
>
> To make this (and in the future the file system implementations) more
> readable also add a symbolic name for the 0 mode used to allocate blocks.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
For a brief moment I wondered if it were possible to set more than one
mode bit but it looks like none of the implementations support that kind
of wackiness (e.g. COLLAPSE|INSERT_RANGE for magicks!) so we're good:
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/open.c | 51 ++++++++++++++++++-------------------
> include/linux/falloc.h | 18 ++++++++-----
> include/uapi/linux/falloc.h | 1 +
> 3 files changed, 38 insertions(+), 32 deletions(-)
>
> diff --git a/fs/open.c b/fs/open.c
> index 22adbef7ecc2a6..daf1b55ca8180b 100644
> --- a/fs/open.c
> +++ b/fs/open.c
> @@ -252,40 +252,39 @@ int vfs_fallocate(struct file *file, int mode, loff_t offset, loff_t len)
> if (offset < 0 || len <= 0)
> return -EINVAL;
>
> - /* Return error if mode is not supported */
> - if (mode & ~FALLOC_FL_SUPPORTED_MASK)
> + if (mode & ~(FALLOC_FL_MODE_MASK | FALLOC_FL_KEEP_SIZE))
> return -EOPNOTSUPP;
>
> - /* Punch hole and zero range are mutually exclusive */
> - if ((mode & (FALLOC_FL_PUNCH_HOLE | FALLOC_FL_ZERO_RANGE)) ==
> - (FALLOC_FL_PUNCH_HOLE | FALLOC_FL_ZERO_RANGE))
> - return -EOPNOTSUPP;
> -
> - /* Punch hole must have keep size set */
> - if ((mode & FALLOC_FL_PUNCH_HOLE) &&
> - !(mode & FALLOC_FL_KEEP_SIZE))
> + /*
> + * Modes are exclusive, even if that is not obvious from the encoding
> + * as bit masks and the mix with the flag in the same namespace.
> + *
> + * To make things even more complicated, FALLOC_FL_ALLOCATE_RANGE is
> + * encoded as no bit set.
> + */
> + switch (mode & FALLOC_FL_MODE_MASK) {
> + case FALLOC_FL_ALLOCATE_RANGE:
> + case FALLOC_FL_UNSHARE_RANGE:
> + case FALLOC_FL_ZERO_RANGE:
> + break;
> + case FALLOC_FL_PUNCH_HOLE:
> + if (!(mode & FALLOC_FL_KEEP_SIZE))
> + return -EOPNOTSUPP;
> + break;
> + case FALLOC_FL_COLLAPSE_RANGE:
> + case FALLOC_FL_INSERT_RANGE:
> + if (mode & FALLOC_FL_KEEP_SIZE)
> + return -EOPNOTSUPP;
> + break;
> + default:
> return -EOPNOTSUPP;
> -
> - /* Collapse range should only be used exclusively. */
> - if ((mode & FALLOC_FL_COLLAPSE_RANGE) &&
> - (mode & ~FALLOC_FL_COLLAPSE_RANGE))
> - return -EINVAL;
> -
> - /* Insert range should only be used exclusively. */
> - if ((mode & FALLOC_FL_INSERT_RANGE) &&
> - (mode & ~FALLOC_FL_INSERT_RANGE))
> - return -EINVAL;
> -
> - /* Unshare range should only be used with allocate mode. */
> - if ((mode & FALLOC_FL_UNSHARE_RANGE) &&
> - (mode & ~(FALLOC_FL_UNSHARE_RANGE | FALLOC_FL_KEEP_SIZE)))
> - return -EINVAL;
> + }
>
> if (!(file->f_mode & FMODE_WRITE))
> return -EBADF;
>
> /*
> - * We can only allow pure fallocate on append only files
> + * On append-only files only space preallocation is supported.
> */
> if ((mode & ~FALLOC_FL_KEEP_SIZE) && IS_APPEND(inode))
> return -EPERM;
> diff --git a/include/linux/falloc.h b/include/linux/falloc.h
> index f3f0b97b167579..3f49f3df6af5fb 100644
> --- a/include/linux/falloc.h
> +++ b/include/linux/falloc.h
> @@ -25,12 +25,18 @@ struct space_resv {
> #define FS_IOC_UNRESVSP64 _IOW('X', 43, struct space_resv)
> #define FS_IOC_ZERO_RANGE _IOW('X', 57, struct space_resv)
>
> -#define FALLOC_FL_SUPPORTED_MASK (FALLOC_FL_KEEP_SIZE | \
> - FALLOC_FL_PUNCH_HOLE | \
> - FALLOC_FL_COLLAPSE_RANGE | \
> - FALLOC_FL_ZERO_RANGE | \
> - FALLOC_FL_INSERT_RANGE | \
> - FALLOC_FL_UNSHARE_RANGE)
> +/*
> + * Mask of all supported fallocate modes. Only one can be set at a time.
> + *
> + * In addition to the mode bit, the mode argument can also encode flags.
> + * FALLOC_FL_KEEP_SIZE is the only supported flag so far.
> + */
> +#define FALLOC_FL_MODE_MASK (FALLOC_FL_ALLOCATE_RANGE | \
> + FALLOC_FL_PUNCH_HOLE | \
> + FALLOC_FL_COLLAPSE_RANGE | \
> + FALLOC_FL_ZERO_RANGE | \
> + FALLOC_FL_INSERT_RANGE | \
> + FALLOC_FL_UNSHARE_RANGE)
>
> /* on ia32 l_start is on a 32-bit boundary */
> #if defined(CONFIG_X86_64)
> diff --git a/include/uapi/linux/falloc.h b/include/uapi/linux/falloc.h
> index 51398fa57f6cdf..5810371ed72bbd 100644
> --- a/include/uapi/linux/falloc.h
> +++ b/include/uapi/linux/falloc.h
> @@ -2,6 +2,7 @@
> #ifndef _UAPI_FALLOC_H_
> #define _UAPI_FALLOC_H_
>
> +#define FALLOC_FL_ALLOCATE_RANGE 0x00 /* allocate range */
> #define FALLOC_FL_KEEP_SIZE 0x01 /* default is extend size */
> #define FALLOC_FL_PUNCH_HOLE 0x02 /* de-allocates range */
> #define FALLOC_FL_NO_HIDE_STALE 0x04 /* reserved codepoint */
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-08-27 14:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 6:50 sort out the fallocate mode mess v2 Christoph Hellwig
2024-08-27 6:50 ` [PATCH 1/6] block: remove checks for FALLOC_FL_NO_HIDE_STALE Christoph Hellwig
2024-08-27 14:55 ` Darrick J. Wong
2024-08-28 14:58 ` Christian Brauner
2024-08-28 15:31 ` Jan Kara
2024-08-27 6:50 ` [PATCH 2/6] ext4: remove tracing " Christoph Hellwig
2024-08-27 14:56 ` Darrick J. Wong
2024-08-28 4:04 ` Christoph Hellwig
2024-08-28 15:31 ` Jan Kara
2024-08-27 6:50 ` [PATCH 3/6] fs: sort out the fallocate mode vs flag mess Christoph Hellwig
2024-08-27 14:55 ` Darrick J. Wong [this message]
2024-08-28 4:05 ` Christoph Hellwig
2024-08-28 15:34 ` Jan Kara
2024-08-27 6:50 ` [PATCH 4/6] xfs: call xfs_flush_unmap_range from xfs_free_file_space Christoph Hellwig
2024-08-27 16:03 ` Darrick J. Wong
2024-08-28 4:06 ` Christoph Hellwig
2024-08-29 3:03 ` Dave Chinner
2024-08-29 3:54 ` Christoph Hellwig
2024-08-27 6:50 ` [PATCH 5/6] xfs: move the xfs_is_always_cow_inode check into xfs_alloc_file_space Christoph Hellwig
2024-08-27 16:03 ` Darrick J. Wong
2024-08-27 6:50 ` [PATCH 6/6] xfs: refactor xfs_file_fallocate Christoph Hellwig
2024-08-27 16:07 ` Darrick J. Wong
2024-08-28 4:07 ` Christoph Hellwig
2024-08-29 3:11 ` Dave Chinner
2024-08-29 3:56 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2024-08-21 6:30 sort out the fallocate mode mess Christoph Hellwig
2024-08-21 6:30 ` [PATCH 3/6] fs: sort out the fallocate mode vs flag mess Christoph Hellwig
2024-08-21 12:43 ` Brian Foster
2024-08-21 13:14 ` Christoph Hellwig
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=20240827145502.GP865349@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=axboe@kernel.dk \
--cc=bfoster@redhat.com \
--cc=brauner@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).