Commit cd6b328c authored Jul 23, 2013 by Bruno Faccini Committed by Greg Kroah-Hartman Jul 23, 2013

staging/lustre/mdc: Keep resend FLocks

FLocks requests (particulary F_UNLCKs) can't be trashed
upon comm problems with Server/MDS nor upon kill/exit,
thus we need to keep retry/send.

Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2665
Lustre-change: http://review.whamcloud.com/6415


Signed-off-by: Bruno Faccini <bruno.faccini@intel.com>
Reviewed-by: Bobi Jam <bobijam@gmail.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
Signed-off-by: Peng Tao <tao.peng@emc.com>
Signed-off-by: Andreas Dilger <andreas.dilger@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

parent 70b749d4

drivers/staging/lustre/lustre/mdc/mdc_locks.c

+7 −1

Original line number	Diff line number	Diff line
		@@ -823,7 +823,13 @@ int mdc_enqueue(struct obd_export exp, struct ldlm_enqueue_info einfo,
		/* For flock requests we immediatelly return without further
		delay and let caller deal with the rest, since rest of
		this function metadata processing makes no sense for flock
		requests anyway */
		requests anyway. But in case of problem during comms with
		Server (ETIMEDOUT) or any signal/kill attempt (EINTR), we
		can not rely on caller and this mainly for F_UNLCKs
		(explicits or automatically generated by Kernel to clean
		current FLocks upon exit) that can't be trashed */
		if ((rc == -EINTR) \|\| (rc == -ETIMEDOUT))
		goto resend;
		RETURN(rc);
		}