All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avinesh Kumar <akumar@suse.de>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] mmap.2: fix missing text
Date: Tue, 29 Aug 2023 16:02:56 +0530	[thread overview]
Message-ID: <3134171.GIylZMhVn5@localhost> (raw)
In-Reply-To: <8be479e0-c851-3442-e6d3-9e3ff39458ae@kernel.org>

Hi Alex,

On Tuesday, August 29, 2023 3:13:17 PM IST Alejandro Colomar wrote:
> Hi Avinesh,
> 
> On 2023-08-28 15:28, Avinesh Kumar wrote:
> >> Was this text accidentally lost in some patch, or was it never added?
> >> If it was there once, please add a "Fixes: ..." tag for it.
> > 
> > I am not sure if it was ever there.
> 
> It was never there, it seems.
Thank you for digging and confirming this. I've send the v2 with "Fixes: ...".
> 
> $ git show 090fdddb43 -- man2/mmap.2
> commit 090fdddb4342f92a1dbeba687462f4bcee816232
> Author: Michael Kerrisk <mtk.manpages@gmail.com>
> Date:   Mon May 17 15:31:08 2021 +1200
> 
>     memfd_create.2, mmap.2, shmget.2: Document the EPERM for huge page
> allocations
> 
>     This error can occur if the caller is does not have CAP_IPC_LOCK
>     and is not a member of the sysctl_hugetlb_shm_group.
> 
>     Reported-by: Yang Xu <xuyang2018.jy@fujitsu.com>
>     Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
> 
> diff --git a/man2/mmap.2 b/man2/mmap.2
> index 03f2eeb2c..4ee2f4f96 100644
> --- a/man2/mmap.2
> +++ b/man2/mmap.2
> @@ -628,6 +628,18 @@ .SH ERRORS
>  The operation was prevented by a file seal; see
>  .BR fcntl (2).
>  .TP
> +.B EPERM
> +The
> +.B MAP_HUGETLB
> +flag was specified, but the caller was not privileged (did not have the
> +.B CAP_IPC_LOCK
> +capability)
> +and is not a member of the
> +.I sysctl_hugetlb_shm_group
> +group; see the description of
> +.I /proc/sys/vm/sysctl_hugetlb_shm_group
> +in
> +.TP
>  .B ETXTBSY
>  .B MAP_DENYWRITE
>  was set but the object specified by
> 
> >> Also, proc(5) was recently cut into little sashimi pieces.  You want
> >> to refer to proc_sys(5).
> > 
> > Ah.. Thanks for pointing this out, I just checked that thread. I'll send
> > the updated patch if you are fine with no "Fixes:" tag for this.
> 
> Please add a Fixes mentioning that commit above.
> 
> Cheers,
> Alex

--
Regards,
Avinesh



      parent reply	other threads:[~2023-08-29 10:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 15:59 [PATCH] mmap.2: fix missing text Avinesh Kumar
2023-08-25 17:52 ` Alejandro Colomar
2023-08-28 13:28   ` Avinesh Kumar
2023-08-29  9:43     ` Alejandro Colomar
2023-08-29  9:47       ` Alejandro Colomar
2023-08-29 10:32       ` Avinesh Kumar [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=3134171.GIylZMhVn5@localhost \
    --to=akumar@suse.de \
    --cc=alx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.