From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Charan Teja Reddy <quic_charante@quicinc.com>
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
minchan@kernel.org, nadav.amit@gmail.com, mtk.manpages@gmail.com
Subject: Re: [PATCH] madvise.2: update EINVAL return info
Date: Thu, 17 Mar 2022 22:02:59 +0100 [thread overview]
Message-ID: <bebd3a92-0828-9e7e-d6b0-51b75e45a124@gmail.com> (raw)
In-Reply-To: <1647442320-7261-1-git-send-email-quic_charante@quicinc.com>
Hellp Charan,
On 3/16/22 15:52, Charan Teja Reddy wrote:
> MADV_COLD and MADV_PAGEOUT advises on an address range which includes
> locked, Huge TLB pages or VM_PFNMAP pages can return EINVAL. Update the
> man pages accordingly.
>
> Reported-by: Nadav Amit <nadav.amit@gmail.com>
> Signed-off-by: Charan Teja Reddy <quic_charante@quicinc.com>
Patch applied.
Thanks,
Alex
> ---
> man2/madvise.2 | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/man2/madvise.2 b/man2/madvise.2
> index f1f384c..ab98a87 100644
> --- a/man2/madvise.2
> +++ b/man2/madvise.2
> @@ -505,6 +505,16 @@ is not a valid.
> .B EINVAL
> .I advice
> is
> +.BR MADV_COLD
> +or
> +.BR MADV_PAGEOUT
> +and the specified address range includes locked, Huge TLB pages, or
> +.B VM_PFNMAP
> +pages.
> +.TP
> +.B EINVAL
> +.I advice
> +is
> .B MADV_DONTNEED
> or
> .BR MADV_REMOVE
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
prev parent reply other threads:[~2022-03-17 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 14:52 Charan Teja Reddy
2022-03-17 21:02 ` Alejandro Colomar (man-pages) [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=bebd3a92-0828-9e7e-d6b0-51b75e45a124@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=nadav.amit@gmail.com \
--cc=quic_charante@quicinc.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
all inboxes | Powered by JetHome®