From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Suren Baghdasaryan <surenb@google.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
linux-mm@kvack.org
Subject: [PATCH man-pages v2] process_madvise.2: describe 6.13 behaviour permitting all madvise flags
Date: Fri, 29 Nov 2024 16:44:22 +0000 [thread overview]
Message-ID: <20241129164422.89837-1-lorenzo.stoakes@oracle.com> (raw)
Since Linux 6.13 it has become possible to use all madvise flags when targeting
the calling process. Update the man page to reflect this change.
Reviewed-by: David Hildenbrand <david@redhat.com>
Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
---
v2:
* Use semantic newlines as suggested by Alejandro.
v1:
https://lore.kernel.org/all/20241129095507.11001-1-lorenzo.stoakes@oracle.com/
man/man2/process_madvise.2 | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/man/man2/process_madvise.2 b/man/man2/process_madvise.2
index b78a61553..2ebbfea44 100644
--- a/man/man2/process_madvise.2
+++ b/man/man2/process_madvise.2
@@ -54,7 +54,9 @@ This value must be less than or equal to
or accessible via the call
.IR sysconf(_SC_IOV_MAX) ).
.P
-The
+If manipulating another process,
+or before Linux 6.13,
+the
.I advice
argument is one of the following values:
.TP
@@ -74,6 +76,10 @@ See
See
.BR madvise (2).
.P
+Starting in Linux 6.13,
+when manipulating the calling process,
+any advice flag is permitted.
+.P
The
.I flags
argument is reserved for future use; currently, this argument must be
--
2.47.1
next reply other threads:[~2024-11-29 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 16:44 Lorenzo Stoakes [this message]
2024-12-04 10:13 ` Alejandro Colomar
2024-12-04 11:43 ` Lorenzo Stoakes
2024-12-05 17:41 ` Vlastimil Babka
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=20241129164422.89837-1-lorenzo.stoakes@oracle.com \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=alx@kernel.org \
--cc=jannh@google.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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