linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: fanchaoting <fanchaoting@cn.fujitsu.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	wireshark-dev@wireshark.org
Subject: Re: [PATCH] wireshark: can't decode callback if didn't caught CREATE_SESSION and SETCLIENTID packets before
Date: Fri, 11 Jan 2013 21:10:20 -0500	[thread overview]
Message-ID: <20130112021020.GA32128@fieldses.org> (raw)
In-Reply-To: <50EFDEEA.4040201@cn.fujitsu.com>

On Fri, Jan 11, 2013 at 05:44:10PM +0800, fanchaoting wrote:
> now i found that nfs kernel use 0x40000000 as callback program number.
> the CREATE_SESSION and SETCLIENTID use 0x40000000 as callback program number,
> and they didn't change it.
>
> but i found that i use wireshark to decode nfsv4 callback procedures, it didn't
> decode them if the wireshark or tcpdump didn't caught CREATE_SESSION and SETCLIENTID
> packets before.

No, this change is incorrect.

It may be true that the current linux client always uses that program
number, but the protocol does allow the client to choose any program
number it wants, and I would not be surprised if other clients use
something different.

There might be some other heuristic we could use to find the callbacks
in the case we didn't capture CREATE_SESSION or SETCLIENTID--maybe it
would be OK to just guess that 4 is the right number in that case--but
we must not ignore the provided cb program in the case where we do see
it.

--b.

> 
> Signed-off-by: Fan Chaoting <fanchaoting@cn.fujitsu.com>
> 
> ---
>  epan/dissectors/packet-nfs.c |   10 ++++------
>  1 file changed, 4 insertions(+), 6 deletions(-)
> 
> diff --git a/epan/dissectors/packet-nfs.c b/epan/dissectors/packet-nfs.c
> index 63d1019..7b5ec88 100644
> --- a/epan/dissectors/packet-nfs.c
> +++ b/epan/dissectors/packet-nfs.c
> @@ -7979,10 +7979,7 @@ dissect_nfs_cb_client4(tvbuff_t *tvb, int offset, proto_tree *tree)
>  {
>  	proto_tree *cb_location = NULL;
>  	proto_item *fitem = NULL;
> -	int cbprog;
>  
> -	cbprog = tvb_get_ntohl(tvb, offset);
> -	reg_callback(cbprog);
>  	offset = dissect_rpc_uint32(tvb, tree, hf_nfs_cb_program, offset);
>  	fitem = proto_tree_add_text(tree, tvb, offset, 0, "cb_location");
>  
> @@ -8991,7 +8988,6 @@ dissect_nfs_argop4(tvbuff_t *tvb, int offset, packet_info *pinfo,
>  	proto_tree *ftree = NULL;
>  	proto_tree *newftree = NULL;
>  	guint32 string_length;
> -	int cbprog;
>  	const char *name = NULL, *source_name = NULL, *dest_name=NULL;
>  	const char *opname=NULL;
>  	guint32 last_fh_hash=0;
> @@ -9012,6 +9008,10 @@ dissect_nfs_argop4(tvbuff_t *tvb, int offset, packet_info *pinfo,
>  		"Operations (count: %u)", ops);
>  	offset += 4;
>  
> +	 /*Now the nfs use '0x40000000' as callback's program number.*/
> +#define CB_PROG 0x40000000
> +	reg_callback(CB_PROG);
> +
>  #define MAX_NFSV4_OPS 128
>  
>  	if (ops > MAX_NFSV4_OPS) {
> @@ -9469,8 +9469,6 @@ dissect_nfs_argop4(tvbuff_t *tvb, int offset, packet_info *pinfo,
>  			offset = dissect_nfs_create_session_flags(tvb, offset, newftree, hf_nfs_create_session_flags_csa);
>  			offset = dissect_rpc_chanattrs4(tvb, offset, newftree, "csa_fore_chan_attrs");
>  			offset = dissect_rpc_chanattrs4(tvb, offset, newftree, "csa_back_chan_attrs");
> -			cbprog = tvb_get_ntohl(tvb, offset);
> -			reg_callback(cbprog);
>  			offset = dissect_rpc_uint32(tvb, newftree, hf_nfs_cb_program, offset);
>  			offset = dissect_rpc_secparms4(tvb, offset, newftree);
>  			break;
> -- 
> 1.7.10.1



  reply	other threads:[~2013-01-12  2:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11  9:44 [PATCH] wireshark: can't decode callback if didn't caught CREATE_SESSION and SETCLIENTID packets before fanchaoting
2013-01-12  2:10 ` J. Bruce Fields [this message]
2013-01-14  5:11   ` fanchaoting

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=20130112021020.GA32128@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=fanchaoting@cn.fujitsu.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=wireshark-dev@wireshark.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).