From: John Garry <john.g.garry@oracle.com>
To: alx@kernel.org
Cc: linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org,
dalias@libc.org, brauner@kernel.org,
John Garry <john.g.garry@oracle.com>
Subject: [PATCH 1/2] readv.2: Document RWF_NOAPPEND flag
Date: Tue, 26 Nov 2024 09:08:46 +0000 [thread overview]
Message-ID: <20241126090847.297371-2-john.g.garry@oracle.com> (raw)
In-Reply-To: <20241126090847.297371-1-john.g.garry@oracle.com>
Document flag introduced in Linux v6.9
Signed-off-by: John Garry <john.g.garry@oracle.com>
---
man/man2/readv.2 | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/man/man2/readv.2 b/man/man2/readv.2
index 78232c19f..836612bbe 100644
--- a/man/man2/readv.2
+++ b/man/man2/readv.2
@@ -238,6 +238,26 @@ However, if the
.I offset
argument is \-1, the current file offset is updated.
.TP
+.BR RWF_NOAPPEND " (since Linux 6.9)"
+The
+.BR pwritev2 ()
+system call does not honor the
+.B O_APPEND
+.BR open (2)
+flag.
+Historically Linux honored
+.B O_APPEND
+flag if set and ignored the offset argument, which is a bug.
+For
+.BR pwritev2 (),
+the
+.I offset
+argument is honored as expected if
+.BR RWF_NOAPPEND
+flag is set, the same as if
+.B O_APPEND
+flag were not set.
+.TP
.BR RWF_ATOMIC " (since Linux 6.11)"
Requires that
writes to regular files in block-based filesystems
--
2.31.1
next prev parent reply other threads:[~2024-11-26 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 9:08 [PATCH 0/2] man2: Document RWF_NOAPPEND John Garry
2024-11-26 9:08 ` John Garry [this message]
2024-11-26 11:52 ` [PATCH 1/2] readv.2: Document RWF_NOAPPEND flag Alejandro Colomar
2024-11-26 11:57 ` John Garry
2025-01-04 20:34 ` Alejandro Colomar
2024-11-26 9:08 ` [PATCH 2/2] io_submit.2: " John Garry
2024-11-26 11:55 ` Alejandro Colomar
2025-01-04 20:36 ` Alejandro Colomar
2024-12-16 10:33 ` [PATCH 0/2] man2: Document RWF_NOAPPEND John Garry
2025-01-04 20:17 ` 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=20241126090847.297371-2-john.g.garry@oracle.com \
--to=john.g.garry@oracle.com \
--cc=alx@kernel.org \
--cc=brauner@kernel.org \
--cc=dalias@libc.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
/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