While 0 is a perfectly valid gss sequence number, the current NetApp filer code
assumes that we'll start with a positive number.  No doubt they'll fix their
code, but we may as well use 1 as the initial sequence number in case some
other implementor makes a similar mistake.


 net/sunrpc/auth_gss/auth_gss.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -puN net/sunrpc/auth_gss/auth_gss.c~gss_seqno_one net/sunrpc/auth_gss/auth_gss.c
--- linux-2.5.70/net/sunrpc/auth_gss/auth_gss.c~gss_seqno_one	2003-06-09 19:53:49.000000000 -0400
+++ linux-2.5.70-bfields/net/sunrpc/auth_gss/auth_gss.c	2003-06-09 19:53:49.000000000 -0400
@@ -238,7 +238,7 @@ gss_parse_init_downcall(struct gss_api_m
 		goto err;
 	}
 	ctx->gc_proc = RPC_GSS_PROC_DATA;
-	ctx->gc_seq = 0;
+	ctx->gc_seq = 1;
 	spin_lock_init(&ctx->gc_seq_lock);
 	atomic_set(&ctx->count,1);
 

_