From ec7cddb4f8d8a59f083034405b9f027ad9293507 Mon Sep 17 00:00:00 2001 From: Bobi Jam Date: Fri, 8 Nov 2024 01:00:46 +0800 Subject: [PATCH] LU-13305 osc: rid of an invalid assertion When osc_cache_truncate_start() race with ldlm lock blocking ast, they would access the same extent, and the ext would has oe_hp set by osc_cache_writeback_range() from the data flush caused by ldlm lock canceling. So the EASSERT(!ext->oe_hp && !ext->oe_urgent, ext) is invalid in this case. Signed-off-by: Bobi Jam Change-Id: I15514c54af598f2a130c0ac0a3f356468b4cdfce Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/56914 Tested-by: jenkins Tested-by: Maloo Reviewed-by: Andreas Dilger Reviewed-by: Qian Yingjin Reviewed-by: Patrick Farrell Reviewed-by: Oleg Drokin --- lustre/osc/osc_cache.c | 1 - 1 file changed, 1 deletion(-) diff --git a/lustre/osc/osc_cache.c b/lustre/osc/osc_cache.c index dafc9d3..a7a97e7 100644 --- a/lustre/osc/osc_cache.c +++ b/lustre/osc/osc_cache.c @@ -2710,7 +2710,6 @@ again: -ext->oe_nr_pages); } /* This extent could be on the full extents list, that's OK */ - EASSERT(!ext->oe_hp && !ext->oe_urgent, ext); if (!list_empty(&ext->oe_link)) list_move_tail(&ext->oe_link, &list); else -- 1.8.3.1