From: Alejandro Colomar <alx.manpages@gmail.com>
To: Nick Gregory <nick@nickgregory.me>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: "ccross@google.com" <ccross@google.com>,
Suren Baghdasaryan <surenb@google.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] prctl.2, proc.5: Document VMA naming
Date: Tue, 3 Jan 2023 11:07:54 +0100 [thread overview]
Message-ID: <0d4be8ad-8de2-92ec-ebf4-3f78586ddaae@gmail.com> (raw)
In-Reply-To: <0bae90d9-ea36-9c3b-13e4-1e73f9fb470e@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 5207 bytes --]
On 1/3/23 11:02, Alejandro Colomar wrote:
> Hello Nick,
>
> On 1/3/23 04:28, Nick Gregory wrote:
>> Bring in prctl man page changes from the patch set by Colin Cross
>> <ccross@google.com> [0], and document the corresponding virtual names in proc.
>>
>> Signed-off-by: Nick Gregory <nick@nickgregory.me>
>
> Please add Colin (and whoever was interested in the patch, which seems to be at
> least Suren and Kees) to the Cc tags.
>
> Cheers,
> Alex
>
>>
>> [0] https://lore.kernel.org/linux-mm/20211019215511.3771969-2-surenb@google.com/
>> ---
>> man2/prctl.2 | 35 +++++++++++++++++++++++++++++++++++
>> man5/proc.5 | 14 ++++++++++++++
>> 2 files changed, 49 insertions(+)
>>
>> diff --git a/man2/prctl.2 b/man2/prctl.2
>> index 74f86ff49..82b8a1b02 100644
>> --- a/man2/prctl.2
>> +++ b/man2/prctl.2
>> @@ -769,6 +769,41 @@ This feature is available only if the kernel is built
>> with the
>> .B CONFIG_CHECKPOINT_RESTORE
>> option enabled.
>> .RE
>> +.\" prctl PR_SET_VMA
>> +.TP
>> +.BR PR_SET_VMA " (since Linux 5.17)"
>> +.\" Commit 9a10064f5625d5572c3626c1516e0bebc6c9fe9b
>> +Sets an attribute specified in
>> +.I arg2
>> +for virtual memory areas starting from
>> +the address specified in
>> +.I arg3
>> +and spanning the size specified in
>> +.IR arg4 .
>> +.I arg5
>> +specifies the value of the attribute to be set.
>> +.IP
>> +Note that assigning an attribute to a virtual memory
>> +area might prevent it from being merged with adjacent virtual
Please use semantic newlines.
man-pages(7):
Use semantic newlines
In the source of a manual page, new sentences should be started on new
lines, long sentences should be split into lines at clause breaks (com‐
mas, semicolons, colons, and so on), and long clauses should be split
at phrase boundaries. This convention, sometimes known as "semantic
newlines", makes it easier to see the effect of patches, which often
operate at the level of individual sentences, clauses, or phrases.
>> +memory areas due to the difference in that attribute's value.
>> +.IP
>> +Currently,
>> +.I arg2
>> +must be one of:
>> +.RS
>> +.TP
>> +.B PR_SET_VMA_ANON_NAME
>> +Set a name for anonymous virtual memory areas.
>> +.I arg5
>> +should be a pointer to a null-terminated string containing the
>> +name. The name length including null byte cannot exceed
>> +80 bytes. If
>> +.I arg5
>> +is NULL, the name of the appropriate
>> +anonymous virtual memory areas will be reset.
>> +The name can contain only printable ascii characters
>> +(including space), except '[',']','\','$' and '`'.
You need to escape several characters here. See groff_char(7):
┌──────────────────────────────────────────────────────────────────┐
│Keycap Appearance and meaning Special character and meaning │
├──────────────────────────────────────────────────────────────────┤
│" " neutral double quote \[dq] neutral double quote │
│' ’ closing single quote \[aq] neutral apostrophe │
│- ‐ hyphen \- or \[-] minus sign/Unix dash │
│\ (escape character) \e or \[rs] reverse solidus │
│^ ˆ modifier circumflex \(ha circumflex/caret/“hat” │
│` ‘ opening single quote \(ga grave accent │
│~ ˜ modifier tilde \(ti tilde │
└──────────────────────────────────────────────────────────────────┘
BTW, although that table doesn't show it, \(dq and \(aq also work for double and
single quotes. Branden, why is that table inconsistent with the style of
special characters?
>> +.RE
>> .\" prctl PR_MPX_ENABLE_MANAGEMENT
>> .TP
>> .BR PR_MPX_ENABLE_MANAGEMENT ", " PR_MPX_DISABLE_MANAGEMENT " (since Linux
>> 3.19, removed in Linux 5.4; only on x86)"
>> diff --git a/man5/proc.5 b/man5/proc.5
>> index 65a4c38e3..e0a64d486 100644
>> --- a/man5/proc.5
>> +++ b/man5/proc.5
>> @@ -1372,6 +1372,20 @@ See
>> .TP
>> .I [heap]
>> The process's heap.
>> +.TP
>> +.IR [anon: name ] " (since Linux 5.17)"
>> +.\" Commit 9a10064f5625d5572c3626c1516e0bebc6c9fe9b
>> +A named private anonymous mapping.
>> +Set with
>> +.BR prctl (2)
>> +.BR PR_SET_VMA_ANON_NAME .
>> +.TP
>> +.IR [anon_shmem: name ] " (since Linux 6.2)"
>> +.\" Commit d09e8ca6cb93bb4b97517a18fbbf7eccb0e9ff43
>> +A named shared anonymous mapping.
>> +Set with
>> +.BR prctl (2)
>> +.BR PR_SET_VMA_ANON_NAME .
>> .in
>> .RE
>> .IP
>
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-01-03 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 3:28 [PATCH] prctl.2, proc.5: Document VMA naming Nick Gregory
2023-01-03 10:02 ` Alejandro Colomar
2023-01-03 10:07 ` Alejandro Colomar [this message]
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=0d4be8ad-8de2-92ec-ebf4-3f78586ddaae@gmail.com \
--to=alx.manpages@gmail.com \
--cc=ccross@google.com \
--cc=g.branden.robinson@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-man@vger.kernel.org \
--cc=nick@nickgregory.me \
--cc=surenb@google.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