All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.ibm.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: Mike Rapoport <rppt@kernel.org>,
	linux-api@vger.kernel.org, linux-man@vger.kernel.org,
	linux-mm@kvack.org, Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH v2] man2: new page describing memfd_secret() system call
Date: Thu, 29 Jul 2021 13:30:20 +0300	[thread overview]
Message-ID: <YQKDPMmyKdKcqHJf@linux.ibm.com> (raw)
In-Reply-To: <3572b371-80ab-eac1-e2c5-26b07748f767@gmail.com>

On Thu, Jul 29, 2021 at 12:12:12PM +0200, Alejandro Colomar (man-pages) wrote:
> Hi Mike,
> 
> On 7/29/21 10:29 AM, Mike Rapoport wrote:
> > From: Mike Rapoport <rppt@linux.ibm.com>
> > 
> > Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
> > ---
> > 
> > v2: address Alex's comments:
> > * update synopsis to match new style for syscalls without a wrapper
> > * drop note about absence of glibc wrapper
> > * update formatting
> 
> Please check a small typo introduced in v2 below.
> 
> Thanks!
> 
> Alex
> 
> > 
> > v1: https://lore.kernel.org/linux-api/20210727124140.1487079-1-rppt@kernel.org
> > 
> >   man2/memfd_secret.2 | 147 ++++++++++++++++++++++++++++++++++++++++++++
> >   1 file changed, 147 insertions(+)
> >   create mode 100644 man2/memfd_secret.2
> > 
> > diff --git a/man2/memfd_secret.2 b/man2/memfd_secret.2
> > new file mode 100644
> > index 000000000..5a70cb5d2
> > --- /dev/null
> > +++ b/man2/memfd_secret.2
> > @@ -0,0 +1,147 @@
> > +.\" Copyright (c) 2021, IBM Corporation.
> > +.\" Written by Mike Rapoport <rppt@linux.ibm.com>
> > +.\"
> > +.\" Based on memfd_create(2) man page
> > +.\" Copyright (C) 2014 Michael Kerrisk <mtk.manpages@gmail.com>
> > +.\" and Copyright (C) 2014 David Herrmann <dh.herrmann@gmail.com>
> > +.\"
> > +.\" %%%LICENSE_START(GPLv2+)
> > +.\"
> > +.\" This program is free software; you can redistribute it and/or modify
> > +.\" it under the terms of the GNU General Public License as published by
> > +.\" the Free Software Foundation; either version 2 of the License, or
> > +.\" (at your option) any later version.
> > +.\"
> > +.\" This program is distributed in the hope that it will be useful,
> > +.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
> > +.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> > +.\" GNU General Public License for more details.
> > +.\"
> > +.\" You should have received a copy of the GNU General Public
> > +.\" License along with this manual; if not, see
> > +.\" <http://www.gnu.org/licenses/>.
> > +.\" %%%LICENSE_END
> > +.\"
> > +.TH MEMFD_SECRET 2 2020-08-02 Linux "Linux Programmer's Manual"
> > +.SH NAME
> > +memfd_secret \- create an anonymous file to access secret memory regions
> > +.SH SYNOPSIS
> > +.nf
> > +.PP
> > +.BR "#include <sys/syscall.h>" "      /* Definition of " SYS_* " constants */"
> > +.B #include <unistd.h>
> > +.PP
> > +.BI "int syscall(SYS_memfd_secret, int " cmd ", unsigned int " flags \
> > +", int " cpu_id );
> 
> Check the parameter list :)
 
Argh. 

Would you need v3 or this on top would suffice?

diff --git a/man2/memfd_secret.2 b/man2/memfd_secret.2
index 5a70cb5d2..8263f18d5 100644
--- a/man2/memfd_secret.2
+++ b/man2/memfd_secret.2
@@ -31,8 +31,7 @@ memfd_secret \- create an anonymous file to access secret memory regions
 .BR "#include <sys/syscall.h>" "      /* Definition of " SYS_* " constants */"
 .B #include <unistd.h>
 .PP
-.BI "int syscall(SYS_memfd_secret, int " cmd ", unsigned int " flags \
-", int " cpu_id );
+.BI "int syscall(SYS_memfd_secret, unsigned int " flags ");
 .fi
 .PP
 .IR Note :

-- 
Sincerely yours,
Mike.

  reply	other threads:[~2021-07-29 10:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29  8:29 [PATCH v2] man2: new page describing memfd_secret() system call Mike Rapoport
2021-07-29 10:12 ` Alejandro Colomar (man-pages)
2021-07-29 10:30   ` Mike Rapoport [this message]
2021-07-29 11:07     ` Alejandro Colomar (man-pages)

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=YQKDPMmyKdKcqHJf@linux.ibm.com \
    --to=rppt@linux.ibm.com \
    --cc=alx.manpages@gmail.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mtk.manpages@gmail.com \
    --cc=rppt@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.