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@xxxxxxxxxx> > --- > 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.
