On Sat, Jun 14, 2008 at 11:58:55AM -0400, Trond Myklebust wrote: > On Fri, 2008-06-13 at 18:50 -0400, J. Bruce Fields wrote: > > The i_lock uses in auth_gss.c are to protect the gc_upcall and gc_ctx > > fields of the gss cred; so we can use a separate per-auth spinlock for > > those instead of the i_lock. This simplifies the locking in the case > > where we have two different pipes (one the current pipe, one the pipe > > for a new more flexible upcall), either of which might be used for gss > > upcalls. > > NACK. I deliberately ripped out the old struct gss_auth spinlock in > order to allow multiple gss_auth per inode (I believe Kevin was asking > for this). OK, makes sense. So what will be the scope of a cred lookup--an rpc client? I wish I had a better picture of what the data structures here will eventually look like. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
