From: Benny Halevy <bhalevy@primarydata.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/4] SQUASHME: pnfsd: nfs4_find_create_layout_stateid
Date: Mon, 07 Oct 2013 18:03:31 +0300 [thread overview]
Message-ID: <5252CD43.6000101@primarydata.com> (raw)
In-Reply-To: <20131006152916.GA8801@infradead.org>
On 2013-10-06 18:29, Christoph Hellwig wrote:
>> + * If the layout state was found in cache, grab a reference count on it;
>> + * otherwise, allocate a new layout state if "do_alloc" is set.
>
> There is no do_alloc parameter to the function.
>
Yup. Silly copy+paste...
>> + *
>> + * Called with the state_lock held
>> + * Returns zero and the layout state in *lsp, or error.
>> + */
>> +static __be32
>> +nfs4_find_create_layout_stateid(struct nfs4_client *clp, struct nfs4_file *fp,
>> + stateid_t *stateid, unsigned char typemask,
>> + struct nfs4_layout_state **lsp)
>> +{
>> + struct nfs4_layout_state *ls = NULL;
>> + __be32 status = 0;
>> + struct nfs4_stid *stid;
>> +
>> + dprintk("--> %s clp %p fp %p operation stateid=" STATEID_FMT "\n",
>> + __func__, clp, fp, STATEID_VAL(stateid));
>> +
>> + nfs4_assert_state_locked();
>> + status = nfsd4_lookup_stateid(stateid, typemask, &stid, true,
>> + net_generic(clp->net, nfsd_net_id));
>> + if (status)
>> + goto out;
>> +
>> + /* Is this the first use of this layout ? */
>> + if (stid->sc_type != NFS4_LAYOUT_STID) {
>> + ls = alloc_init_layout_state(clp, fp, stateid);
>> + if (!ls) {
>> + status = nfserr_jukebox;
>> + goto out;
>> + }
>> + } else {
>> + ls = container_of(stid, struct nfs4_layout_state, ls_stid);
>> +
>> + /* BAD STATEID */
>> + if (stateid->si_generation > ls->ls_stid.sc_stateid.si_generation) {
>> + status = nfserr_bad_stateid;
>> + goto out;
>> + }
>> + get_layout_state(ls);
>> + }
>> + status = 0;
>> +
>> + dprintk("%s: layout stateid=" STATEID_FMT " ref=%d\n", __func__,
>> + STATEID_VAL(&ls->ls_stid.sc_stateid), atomic_read(&ls->ls_ref.refcount));
>> +
>> + *lsp = ls;
>> +out:
>> + dprintk("<-- %s status %d\n", __func__, htonl(status));
>> +
>> + return status;
>> +}
>
> Shouldn't there be a corresponding removal of the alloc code from
> nfs4_process_layout_stateid?
Yes, the corresponding code in nfs4_process_layout_stateid
can and should be removed.
I'll resend a new version of this patch.
Thanks!
Benny
>
> --
> 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
>
next prev parent reply other threads:[~2013-10-07 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 7:40 [PATCH 0/4] pnfsd: refactor nfs4_process_layout_stateid Benny Halevy
2013-10-06 7:44 ` [PATCH 1/4] SQUASHME: fix lo_destroy_list nested definition Benny Halevy
2013-10-06 7:44 ` [PATCH 2/4] SQUASHME: pnfsd: nfs4_find_create_layout_stateid Benny Halevy
2013-10-06 15:29 ` Christoph Hellwig
2013-10-07 15:03 ` Benny Halevy [this message]
2013-10-07 15:45 ` [PATCH v2 " Benny Halevy
2013-10-06 7:44 ` [PATCH 3/4] SQUASHME: pnfsd: no need for find_file in layout commit/return Benny Halevy
2013-10-06 15:30 ` Christoph Hellwig
2013-10-07 15:50 ` [PATCH v2 " Benny Halevy
2013-10-06 7:44 ` [PATCH 4/4] SQUASHME: pnfsd: fixup error code for layout_commit Benny Halevy
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=5252CD43.6000101@primarydata.com \
--to=bhalevy@primarydata.com \
--cc=hch@infradead.org \
--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).