On Fri, Nov 29, 2024 at 01:14:08PM +0100, David Hildenbrand wrote: > On 29.11.24 10:55, Lorenzo Stoakes wrote: > > 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. > > > > Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx> > > --- > > man/man2/process_madvise.2 | 5 ++++- > > 1 file changed, 4 insertions(+), 1 deletion(-) > > > > diff --git a/man/man2/process_madvise.2 b/man/man2/process_madvise.2 > > index b78a61553..d12407bdb 100644 > > --- a/man/man2/process_madvise.2 > > +++ b/man/man2/process_madvise.2 > > @@ -54,7 +54,7 @@ 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 prior to Linux 6.13, the > > .I advice > > argument is one of the following values: > > .TP > > @@ -74,6 +74,9 @@ 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 > > I was briefly concerned when reading the subject, then I realized here > "calling process" :) Haha yes, I did wonder how that would sound when I wrote it, but sort of ran out of space in the subject and hoped the commit message would reduce panic :P > > Reviewed-by: David Hildenbrand <david@xxxxxxxxxx> Thanks! > > -- > Cheers, > > David / dhildenb >
