[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f42f9a79-75cf-491e-bf46-5ea036cf6656@huawei.com>
Date: Tue, 15 Jul 2025 20:50:16 +0800
From: Zhang Yi <yi.zhang@...wei.com>
To: chuguangqing <chuguangqing@...pur.com>
CC: <linux-ext4@...r.kernel.org>, <linux-kernel@...r.kernel.org>, Theodore
Ts'o <tytso@....edu>, Andreas Dilger <adilger.kernel@...ger.ca>
Subject: Re: [PATCH 1/1] ext4: add FALLOC_FL_ALLOCATE_RANGE to supported flags
mask
On 2025/7/15 14:45, chuguangqing wrote:
> Note that since FALLOC_FL_ALLOCATE_RANGE is defined as 0x00, this addition
> has no functional modifications.
>
> Signed-off-by: chuguangqing <chuguangqing@...pur.com>
> ---
> fs/ext4/extents.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index b43aa82c1b39..f0f9363fd9fd 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -4784,9 +4784,9 @@ long ext4_fallocate(struct file *file, int mode, loff_t offset, loff_t len)
> return -EOPNOTSUPP;
>
> /* Return error if mode is not supported */
> - if (mode & ~(FALLOC_FL_KEEP_SIZE | FALLOC_FL_PUNCH_HOLE |
> - FALLOC_FL_ZERO_RANGE | FALLOC_FL_COLLAPSE_RANGE |
> - FALLOC_FL_INSERT_RANGE | FALLOC_FL_WRITE_ZEROES))
> + if (mode & ~(FALLOC_FL_ALLOCATE_RANGE | FALLOC_FL_KEEP_SIZE |
> + FALLOC_FL_PUNCH_HOLE | FALLOC_FL_COLLAPSE_RANGE |
> + FALLOC_FL_ZERO_RANGE | FALLOC_FL_INSERT_RANGE))
> return -EOPNOTSUPP;
>
> inode_lock(inode);
Why did you remove the FALLOC_FL_WRITE_ZEROES support?
Regards,
Yi.
Powered by blists - more mailing lists