From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Uwe Kleine-K??nig <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 04/11] nfs: shorten and simplify rpc_add_credentials a bit
Date: Sat, 8 Feb 2014 07:51:28 +0100 [thread overview]
Message-ID: <20140208065128.GM9671@ns203013.ovh.net> (raw)
In-Reply-To: <1391808493-27328-4-git-send-email-u.kleine-koenig@pengutronix.de>
On 22:28 Fri 07 Feb , Uwe Kleine-K??nig wrote:
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
keep the hostname I use it on nfs for export filter
Best Regards,
J.
> ---
> fs/nfs.c | 26 +++++---------------------
> 1 file changed, 5 insertions(+), 21 deletions(-)
>
> diff --git a/fs/nfs.c b/fs/nfs.c
> index 76d8c0595db4..54dda261c0b1 100644
> --- a/fs/nfs.c
> +++ b/fs/nfs.c
> @@ -224,34 +224,18 @@ out_overflow:
> */
> static uint32_t *rpc_add_credentials(uint32_t *p)
> {
> - int hl;
> - int hostnamelen = 0;
> -
> /*
> - * Here's the executive summary on authentication requirements of the
> - * various NFS server implementations: Linux accepts both AUTH_NONE
> - * and AUTH_UNIX authentication (also accepts an empty hostname field
> - * in the AUTH_UNIX scheme). *BSD refuses AUTH_NONE, but accepts
> - * AUTH_UNIX (also accepts an empty hostname field in the AUTH_UNIX
> - * scheme). To be safe, use AUTH_UNIX and pass the hostname if we have
> - * it (if the BOOTP/DHCP reply didn't give one, just use an empty
> - * hostname).
> + * *BSD refuses AUTH_NONE, so use AUTH_UNIX. An empty hostname is OK for
> + * both Linux and *BSD.
> */
>
> - hl = (hostnamelen + 3) & ~3;
> -
> /* Provide an AUTH_UNIX credential. */
> *p++ = htonl(1); /* AUTH_UNIX */
> - *p++ = htonl(hl + 20); /* auth length */
> + *p++ = htonl(20); /* auth length: 20 + strlen(hostname) */
> *p++ = htonl(0); /* stamp */
> - *p++ = htonl(hostnamelen); /* hostname string */
> -
> - if (hostnamelen & 3)
> - *(p + hostnamelen / 4) = 0; /* add zero padding */
> -
> - /* memcpy(p, hostname, hostnamelen); */ /* empty hostname */
> + *p++ = htonl(0); /* hostname string length */
> + /* memcpy(p, "", 0); p += 0; <- empty host name */
>
> - p += hl / 4;
> *p++ = 0; /* uid */
> *p++ = 0; /* gid */
> *p++ = 0; /* auxiliary gid list */
> --
> 1.8.5.2
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-02-08 6:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 21:28 [PATCH v2 01/11] net: net_read_uint32: assert that only 32 bit are read Uwe Kleine-König
2014-02-07 21:28 ` [PATCH v2 02/11] nfs: fix mount prog version in portmap lookup Uwe Kleine-König
2014-02-07 21:28 ` [PATCH v2 03/11] nfs: skip over stale rpc packets Uwe Kleine-König
2014-02-07 21:28 ` [PATCH v2 04/11] nfs: shorten and simplify rpc_add_credentials a bit Uwe Kleine-König
2014-02-08 6:51 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2014-02-08 15:11 ` Uwe Kleine-König
2014-02-07 21:28 ` [PATCH v2 05/11] nfs: simplify rpc_lookup_req Uwe Kleine-König
2014-02-07 21:28 ` [PATCH v2 06/11] nfs: drop an unneeded variable from nfs_do_open() Uwe Kleine-König
2014-02-07 21:28 ` [PATCH v2 07/11] net: new function net_read_uint64 Uwe Kleine-König
2014-02-07 21:28 ` [PATCH v2 08/11] net: provide alternatives to {ntoh, hton}[sl] funtions with cleaner semantics Uwe Kleine-König
2014-02-07 21:28 ` [PATCH v2 09/11] nfs: switch to nfs3 Uwe Kleine-König
2014-02-07 21:28 ` [PATCH v2 10/11] mount: support filesystem options passed via -o Uwe Kleine-König
2014-02-07 21:28 ` [PATCH v2 11/11] nfs: parse nfsport and mount port from file system options Uwe Kleine-König
2014-02-10 8:02 ` [PATCH v2 01/11] net: net_read_uint32: assert that only 32 bit are read Sascha Hauer
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=20140208065128.GM9671@ns203013.ovh.net \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=u.kleine-koenig@pengutronix.de \
/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