From: Benny Halevy <bhalevy@tonian.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 4/5] nfsd: add a header describing upcall to nfsdcld
Date: Mon, 19 Dec 2011 14:08:19 +0200 [thread overview]
Message-ID: <4EEF2933.8090405@tonian.com> (raw)
In-Reply-To: <1323974606-16477-5-git-send-email-jlayton@redhat.com>
On 2011-12-15 20:43, Jeff Layton wrote:
> The daemon takes a versioned binary struct. Hopefully this should allow
> us to revise the struct later if it becomes necessary.
>
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
> include/linux/nfsd/cld.h | 57 ++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 57 insertions(+), 0 deletions(-)
> create mode 100644 include/linux/nfsd/cld.h
>
> diff --git a/include/linux/nfsd/cld.h b/include/linux/nfsd/cld.h
> new file mode 100644
> index 0000000..d64a7e7
> --- /dev/null
> +++ b/include/linux/nfsd/cld.h
> @@ -0,0 +1,57 @@
> +/*
> + * fs/nfsd/cld.h - upcall description for nfsdcld communication
> + *
> + * Copyright (c) 2011 Red Hat, Inc.
> + * Author(s): Jeff Layton <jlayton@redhat.com>
> + *
> + * 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 program; if not, write to the Free Software
> + * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
> + */
> +
> +#ifndef _NFSD_CLD_H
> +#define _NFSD_CLD_H
> +
> +/* latest upcall version available */
> +#define CLD_MAX_UPCALL_VERSION 1
> +
> +/* defined by RFC3530 */
> +#define NFS4_OPAQUE_LIMIT 1024
> +
> +enum cld_command {
> + Cld_Create, /* create a record for this cm_id */
> + Cld_Expire, /* remove record for this cm_id */
> + Cld_Allow, /* is this cm_id allowed? */
> + Cld_GraceDone, /* grace period is complete */
> + Cld_NrToReclaim, /* how many client records need reclaim? */
> +};
> +
> +/* representation of long-form NFSv4 client ID */
> +struct cld_name {
> + uint16_t cn_len; /* length of cm_id */
> + unsigned char cn_id[NFS4_OPAQUE_LIMIT]; /* client-provided */
> +} __attribute__((packed));
> +
> +/* message struct for communication with userspace */
> +struct cld_msg {
> + uint8_t cm_vers; /* upcall version */
> + uint8_t cm_cmd; /* upcall command */
> + uint32_t cm_xid; /* transaction id */
> + int16_t cm_status; /* return code */
How about swapping the xid and status members so they'd align better?
Benny
> + union {
> + int64_t cm_gracetime; /* grace period start time */
> + struct cld_name cm_name;
> + } __attribute__((packed)) cm_u;
> +} __attribute__((packed));
> +
> +#endif /* !_NFSD_CLD_H */
next prev parent reply other threads:[~2011-12-19 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 18:43 [PATCH v2 0/5] nfsd: overhaul the client name tracking code (RFC) Jeff Layton
2011-12-15 18:43 ` [PATCH v2 1/5] nfsd: add nfsd4_client_tracking_ops struct and a way to set it Jeff Layton
2011-12-15 18:43 ` [PATCH v2 2/5] sunrpc: create nfsd dir in rpc_pipefs Jeff Layton
2011-12-15 18:43 ` [PATCH v2 3/5] nfsd: add a generic flags field to nfs4_client Jeff Layton
2011-12-15 18:43 ` [PATCH v2 4/5] nfsd: add a header describing upcall to nfsdcld Jeff Layton
2011-12-19 12:08 ` Benny Halevy [this message]
2011-12-20 12:45 ` Jeff Layton
2011-12-15 18:43 ` [PATCH v2 5/5] nfsd: add the infrastructure to handle the cld upcall Jeff Layton
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=4EEF2933.8090405@tonian.com \
--to=bhalevy@tonian.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@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.