Commit 15f13cde authored Feb 28, 2014 by Ann Koehler Committed by Greg Kroah-Hartman Feb 28, 2014

lustre/osc: Don't flush active extents.



The extent is active so we need to abort and let the caller
re-dirty the page. If we continued on here, and we were the
one making the extent active, we could deadlock waiting for
the page writeback to clear but it won't because the extent
is active and won't be written out.

Signed-off-by: Ann Koehler <amk@cray.com>
Reviewed-on: http://review.whamcloud.com/8278
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4253


Reviewed-by: Jinshan Xiong <jinshan.xiong@intel.com>
Reviewed-by: Alex Zhuravlev <alexey.zhuravlev@intel.com>
Reviewed-by: Alexey Lyashkov <alexey_lyashkov@xyratex.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
Signed-off-by: Oleg Drokin <oleg.drokin@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

parent 6fd67d85

drivers/staging/lustre/lustre/osc/osc_cache.c

+6 −0

Original line number	Diff line number	Diff line
		@@ -2394,6 +2394,12 @@ int osc_flush_async_page(const struct lu_env env, struct cl_io io,
		* really sending the RPC. */
		case OES_TRUNC:
		/* race with truncate, page will be redirtied */
		case OES_ACTIVE:
		/* The extent is active so we need to abort and let the caller
		* re-dirty the page. If we continued on here, and we were the
		* one making the extent active, we could deadlock waiting for
		* the page writeback to clear but it won't because the extent
		* is active and won't be written out. */
		GOTO(out, rc = -EAGAIN);
		default:
		break;

Admin message