On Tue, 31 May 2011 15:54:36 -0500 Steve French <smfrench@xxxxxxxxx> wrote: > we will have more info when run with he quick and dirty modified logging > I'm not sure what that is, but what may be helpful is to launch a kernel debugger when this happens, track down the TCP_Server_Info and see what the state of the socket that hangs off of it is. If it's a NULL pointer or an already-closed socket, then that may help point the way to the root cause. > On Tue, May 31, 2011 at 3:53 PM, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: > > On 05/31/2011 01:51 PM, Steve French wrote: > >> > >> On Tue, May 31, 2011 at 3:44 PM, Jeff Layton<jlayton@xxxxxxxxxx> Âwrote: > > > >>> Fixing it looks to be anything but trivial. I'm not even quite sure how > >>> to approach it at this point. Suggestions welcome. > >> > >> I thought the kernel was more recent than that - how recent is the kernel > >> here? > >> > >> I think something related to cifs_sendv returning ENOTSOCK immediately > >> when not reconnected could be related. > > > > My kernel is 2.6.38.7, quite recent. ÂWe're using the bind-to-local-IP > > features too, but not sure that matters. > > > > Ben > > > > -- > > Ben Greear <greearb@xxxxxxxxxxxxxxx> > > Candela Technologies Inc Âhttp://www.candelatech.com > > > > > > > -- Jeff Layton <jlayton@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
