From: Pankaj Raghav <p.raghav@samsung.com>
To: linux-man@vger.kernel.org, Alejandro Colomar <alx@kernel.org>
Cc: pankaj.raghav@linux.dev, hch@lst.de,
Zhang Yi <yi.zhang@huaweicloud.com>,
linux-xfs@vger.kernel.org, gost.dev@samsung.com,
"Darrick J . Wong" <djwong@kernel.org>,
linux-ext4@vger.kernel.org, Pankaj Raghav <p.raghav@samsung.com>
Subject: [PATCH v2] man2/fallocate.2: add doc for FALLOC_FL_WRITE_ZEROES
Date: Thu, 20 Aug 2026 11:04:00 +0200 [thread overview]
Message-ID: <20260820090400.857720-1-p.raghav@samsung.com> (raw)
This flag was added to the kernel in v6.17. As of now, only ext4 and
block device nodes support this flag.
Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
---
Changes since v1:
- Change the phrasing around zeroing and its condition (Zhang Yi)
- Update ext4 support only for extent-based files (Zhang Yi)
Note:
This feature was recently added to XFS and it is expected to land in
v7.13. I will update this man page again once v7.13 is released.
man/man2/fallocate.2 | 38 ++++++++++++++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
diff --git a/man/man2/fallocate.2 b/man/man2/fallocate.2
index ef6586c77..48a8c3468 100644
--- a/man/man2/fallocate.2
+++ b/man/man2/fallocate.2
@@ -244,6 +244,43 @@ SMB3 (since Linux 3.17)
.IP \[bu]
Btrfs (since Linux 4.16)
.\" commit f27451f229966874a8793995b8e6b74326d125df
+.SS Writing zeroes in file space
+Specifying the
+.B FALLOC_FL_WRITE_ZEROES
+flag (available since Linux 6.17)
+.\" commit 7bd43cc79cab3850f34da0a31d5b042b701590ef
+in
+.I mode
+physically zeros space in the byte range starting at
+.I offset
+and continuing for
+.I size
+bytes.
+Within the specified range,
+blocks are preallocated for the regions that span the holes
+in the file.
+After a successful call,
+subsequent reads from this range will return zeros and
+subsequent writes to that range do not require further
+changes to the file mapping metadata.
+.P
+Zeroing is done within the filesystem.
+The filesystem may use a hardware-accelerated zeroing command
+or may submit regular writes.
+The behavior depends on the filesystem design and the
+available hardware.
+.P
+No other flags may be specified in
+.I mode
+in conjunction with
+.BR FALLOC_FL_WRITE_ZEROES .
+.P
+Not all filesystems support
+.BR FALLOC_FL_WRITE_ZEROES ;
+if a filesystem doesn't support the operation, an error is returned.
+The operation is supported only in ext4 (only for extent-based files)
+since Linux 6.17.
+.\" commit f4265b8d32c49ff95711e6fef7d05245a2905b30
.SS Increasing file space
Specifying the
.B FALLOC_FL_INSERT_RANGE
@@ -385,6 +422,7 @@ or
is
.BR FALLOC_FL_COLLAPSE_RANGE ,
.BR FALLOC_FL_ZERO_RANGE ,
+.BR FALLOC_FL_WRITE_ZEROES ,
or
.BR FALLOC_FL_INSERT_RANGE ,
but the file referred to by
base-commit: d926b42e0ea0406d5c2556e18205eced92d053f1
--
2.51.2
next reply other threads:[~2026-08-20 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 9:04 Pankaj Raghav [this message]
2026-08-20 9:28 ` [PATCH v2] man2/fallocate.2: add doc for FALLOC_FL_WRITE_ZEROES Alejandro Colomar
2026-08-20 9:31 ` Pankaj Raghav
2026-08-21 3:39 ` Zhang Yi
2026-08-22 12:41 ` Alejandro Colomar
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=20260820090400.857720-1-p.raghav@samsung.com \
--to=p.raghav@samsung.com \
--cc=alx@kernel.org \
--cc=djwong@kernel.org \
--cc=gost.dev@samsung.com \
--cc=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=pankaj.raghav@linux.dev \
--cc=yi.zhang@huaweicloud.com \
/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