From: Benny Halevy <bhalevy@tonian.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Tigran Mkrtchyan <kofemann@googlemail.com>,
linux-nfs@vger.kernel.org, Tigran Mkrtchyan <kofemann@gmail.com>
Subject: Re: [PATCH] nfsd41: handle current stateid in open and close
Date: Tue, 13 Dec 2011 09:47:23 +0200 [thread overview]
Message-ID: <4EE7030B.8050601@tonian.com> (raw)
In-Reply-To: <20111212224025.GB22927@fieldses.org>
On 2011-12-13 00:40, J. Bruce Fields wrote:
> On Thu, Dec 08, 2011 at 06:09:07PM +0200, Benny Halevy wrote:
>> On 2011-12-07 19:11, J. Bruce Fields wrote:
>>> On Wed, Dec 07, 2011 at 03:17:48PM +0200, Benny Halevy wrote:
>>>> On 2011-12-07 01:08, J. Bruce Fields wrote:
>>>>> It's a little verbose, but yes it does nicely collect the current
>>>>> stateid getting/setting into one place. Benny, is the more or less what
>>>>> you were thinking of?
>>>>
>>>> Yes it is, though I also liked your direction of just using the current
>>>> stateid for xdr decoding and encoding.
>>>
>>> I'd still have a slight preference for doing it that way, just because
>>> it would take fewer lines of code--but I can live with this too, so I'll
>>> leave the choice to Tigran's excellent taste....
>>>
>>>> { ~0, { { ~0, ~0 }, ~0 } } is ugly but compact :)
>>>>
>>>> And the following may be an overkill...
>>>> {
>>>> .si_generation = ~0,
>>>> .si_opaque = {
>>>> .so_clid = {
>>>> .cl_boot = ~0,
>>>> .cl_id = ~0,
>>>> },
>>>> .so_id = ~0
>>>> }
>>>> };
>>>
>>> Reminding myself of http://tools.ietf.org/html/rfc5661#section-8.2.3...
>>> "Stateid values whose "other" field is either all zeros or all ones are
>>> reserved."
>>>
>>> Maybe:
>>>
>>> #define all_ones {{~0,~0 },~0}
>>> #define all_zeroes {{ 0, 0 }, 0}
>>> const stateid_t one_stateid = {
>>> .si_generation = ~0,
>>> .si_opaque = all_ones
>>> };
>>
>> That looks like a good compromise to me.
>>
>>> const stateid_t current_stateid = {
>>> .si_generation = 1,
>>> .si_opaque = all_zeroes
>>> };
>>> ...
>>>
>>> Or you could ditch the all_zeroes; it's just there for some kind of
>>> symmetry.
>>
>> Yeah, static initialization to zero is guaranteed.
>
> OK, applying the following assuming no objections.--b.
Ack
Benny
>
> commit f32f3c2d3f09a586349ca9180885dc8741290fd9
> Author: J. Bruce Fields <bfields@redhat.com>
> Date: Mon Dec 12 15:00:35 2011 -0500
>
> nfsd4: initialize special stateid's at compile time
>
> Stateid's with "other" ("opaque") field all zeros or all ones are
> reserved. We define all_ones separately on the off chance there will be
> more such some day, though currently all the other special stateid's
> have zero other field.
>
> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
>
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index 6ab6779..213da7b 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -49,12 +49,20 @@
> time_t nfsd4_lease = 90; /* default lease time */
> time_t nfsd4_grace = 90;
> static time_t boot_time;
> -static stateid_t zerostateid; /* bits all 0 */
> -static stateid_t onestateid; /* bits all 1 */
> +
> +#define all_ones {{~0,~0},~0}
> +static const stateid_t one_stateid = {
> + .si_generation = ~0,
> + .si_opaque = all_ones,
> +};
> +static const stateid_t zero_stateid = {
> + /* all fields zero */
> +};
> +
> static u64 current_sessionid = 1;
>
> -#define ZERO_STATEID(stateid) (!memcmp((stateid), &zerostateid, sizeof(stateid_t)))
> -#define ONE_STATEID(stateid) (!memcmp((stateid), &onestateid, sizeof(stateid_t)))
> +#define ZERO_STATEID(stateid) (!memcmp((stateid), &zero_stateid, sizeof(stateid_t)))
> +#define ONE_STATEID(stateid) (!memcmp((stateid), &one_stateid, sizeof(stateid_t)))
>
> /* forward declarations */
> static int check_for_locks(struct nfs4_file *filp, struct nfs4_lockowner *lowner);
> @@ -4564,7 +4572,6 @@ nfs4_state_init(void)
> }
> for (i = 0; i < LOCKOWNER_INO_HASH_SIZE; i++)
> INIT_LIST_HEAD(&lockowner_ino_hashtbl[i]);
> - memset(&onestateid, ~0, sizeof(stateid_t));
> INIT_LIST_HEAD(&close_lru);
> INIT_LIST_HEAD(&client_lru);
> INIT_LIST_HEAD(&del_recall_lru);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-12-13 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 21:44 [PATCH] nfsd41: handle current stateid in open and close Tigran Mkrtchyan
2011-12-06 23:08 ` J. Bruce Fields
2011-12-07 13:17 ` Benny Halevy
2011-12-07 15:15 ` J. Bruce Fields
2011-12-07 17:11 ` J. Bruce Fields
2011-12-07 17:17 ` Tiramisu Mokka
2011-12-08 16:09 ` Benny Halevy
2011-12-12 22:40 ` J. Bruce Fields
2011-12-13 7:47 ` Benny Halevy [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=4EE7030B.8050601@tonian.com \
--to=bhalevy@tonian.com \
--cc=bfields@fieldses.org \
--cc=kofemann@gmail.com \
--cc=kofemann@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).