On 12/17/2010 08:38 PM, Jeff Layton wrote: > In order to incorporate async requests, we need to allow for a more > general way to do things on receive, rather than just waking up a > process. > > Turn the task pointer in the mid_q_entry into a callback function and a > generic data pointer. When a response comes in, or the socket is > reconnected, cifsd can call the callback function in order to wake up > the process. > > The default is to just wake up the current process which should mean no > change in behavior for existing code. > > Also, clean up the locking in cifs_reconnect. There doesn't seem to be > any need to hold both the srv_mutex and GlobalMid_Lock when walking the > list of mids. > > Signed-off-by: Jeff Layton <jlayton@xxxxxxxxxx> > --- > fs/cifs/cifs_debug.c | 8 +++--- > fs/cifs/cifsglob.h | 15 ++++++++++++- > fs/cifs/connect.c | 56 +++++++++++++++++++++++++------------------------- > fs/cifs/transport.c | 19 +++++++++++++++- > 4 files changed, 63 insertions(+), 35 deletions(-) > Looks good to me. Reviewed-by: Suresh Jayaraman <sjayaraman@xxxxxxx> -- 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
