All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kinglong Mee <kinglongmee@gmail.com>
Cc: bfields@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] Add missing recording of back channel attrs in nfsd4_session
Date: Mon, 2 Dec 2013 11:55:05 -0500	[thread overview]
Message-ID: <20131202165505.GL1960@fieldses.org> (raw)
In-Reply-To: <2BCCA4EF-9FCC-4320-85E1-AD500467C95D@gmail.com>

On Tue, Nov 26, 2013 at 10:25:20PM +0800, Kinglong Mee wrote:
> commit 5b6feee9608dce7afd2646f457c93e612526d1d8 forgot
> recording the back channel attrs in nfsd4_session.
> 
> nfsd just check the back channel attars by check_backchannel_attrs,
> but do not  record it in nfsd4_session in the latest kernel.

Whoops.  So the current server is returning random uninitialized data in
those fields, or all zeros?

It would be easy enough to write a pynfs test for this, I think.

--b.

> 
> Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
> ---
>  fs/nfsd/nfs4state.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index 105d6fa..1aed9be 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -999,6 +999,8 @@ static void init_session(struct svc_rqst *rqstp, struct nfsd4_session *new, stru
>  	spin_unlock(&nn->client_lock);
>  	memcpy(&new->se_fchannel, &cses->fore_channel,
>  			sizeof(struct nfsd4_channel_attrs));
> +	memcpy(&new->se_bchannel, &cses->back_channel,
> +			sizeof(struct nfsd4_channel_attrs));
>  	if (cses->flags & SESSION4_BACK_CHAN) {
>  		struct sockaddr *sa = svc_addr(rqstp);
>  		/*
> -- 
> 1.8.1.4
> 

       reply	other threads:[~2013-12-02 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2BCCA4EF-9FCC-4320-85E1-AD500467C95D@gmail.com>
2013-12-02 16:55 ` J. Bruce Fields [this message]
2013-12-03  2:08   ` [PATCH] Add missing recording of back channel attrs in nfsd4_session Kinglong Mee
2013-12-06 21:12     ` J. Bruce Fields
2013-12-09  1:35       ` Kinglong Mee

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=20131202165505.GL1960@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bfields@redhat.com \
    --cc=kinglongmee@gmail.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.