public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>,
	"G. Branden Robinson" <branden@debian.org>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page nfsservctl.2
Date: Wed, 1 Nov 2023 16:44:11 +0100	[thread overview]
Message-ID: <ZUJyTDKvLzinqOyy@debian> (raw)
In-Reply-To: <ZUJaY4vT3lwVt9mq@meinfjell.helgefjelltest.de>

[-- Attachment #1: Type: text/plain, Size: 1650 bytes --]

Hi Helge, Branden,

On Wed, Nov 01, 2023 at 02:02:11PM +0000, Helge Kreutzmann wrote:
> Without further ado, the following was found:
> 
> Issue:    mountd(8) → B<mountd>(8)
> "/*\n"
> " * These are the commands understood by nfsctl().\n"
> " */\n"
> "#define NFSCTL_SVC        0  /* This is a server process. */\n"
> "#define NFSCTL_ADDCLIENT  1  /* Add an NFS client. */\n"
> "#define NFSCTL_DELCLIENT  2  /* Remove an NFS client. */\n"
> "#define NFSCTL_EXPORT     3  /* Export a filesystem. */\n"
> "#define NFSCTL_UNEXPORT   4  /* Unexport a filesystem. */\n"
> "#define NFSCTL_UGIDUPDATE 5  /* Update a client\\[aq]s UID/GID map\n"
> "                                (only in Linux 2.4.x and earlier). */\n"
> "#define NFSCTL_GETFH      6  /* Get a file handle (used by mountd(8))\n"

Since Branden is going to patch these things soon, and it will likely
affect his script, I'll let him decide what to do here.

Cheers,
Alex

> "                                (only in Linux 2.4.x and earlier). */\n"
> "\\&\n"
> "struct nfsctl_arg {\n"
> "    int                       ca_version;     /* safeguard */\n"
> "    union {\n"
> "        struct nfsctl_svc     u_svc;\n"
> "        struct nfsctl_client  u_client;\n"
> "        struct nfsctl_export  u_export;\n"
> "        struct nfsctl_uidmap  u_umap;\n"
> "        struct nfsctl_fhparm  u_getfh;\n"
> "        unsigned int          u_debug;\n"
> "    } u;\n"
> "}\n"
> "\\&\n"
> "union nfsctl_res {\n"
> "        struct knfs_fh          cr_getfh;\n"
> "        unsigned int            cr_debug;\n"
> "};\n"

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-11-01 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 14:02 Issue in man page nfsservctl.2 Helge Kreutzmann
2023-11-01 15:44 ` Alejandro Colomar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-11 17:13 Helge Kreutzmann
2023-03-11 23:31 ` Alejandro Colomar
2023-03-12  5:23   ` Helge Kreutzmann
2023-03-12 17:11     ` G. Branden Robinson
2023-03-12 17:55       ` Helge Kreutzmann
2023-01-22 19:31 Helge Kreutzmann

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=ZUJyTDKvLzinqOyy@debian \
    --to=alx@kernel.org \
    --cc=branden@debian.org \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.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