From: Hou Tao Date: Tue, 2 Jul 2019 14:35:48 +0000 (+0800) Subject: raid1: use an int as the return value of raise_barrier() X-Git-Tag: v5.15~5523^2~99^2~8 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=4675719d0f47d18bc13db62bd21cffd4e4ec8001;p=platform%2Fkernel%2Flinux-starfive.git raid1: use an int as the return value of raise_barrier() Using a sector_t as the return value is misleading, because raise_barrier() only return 0 or -EINTR. Also add comments for the return values of raise_barrier(). Signed-off-by: Hou Tao Signed-off-by: Song Liu --- diff --git a/drivers/md/raid1.c b/drivers/md/raid1.c index 34e2683..108c750 100644 --- a/drivers/md/raid1.c +++ b/drivers/md/raid1.c @@ -872,8 +872,11 @@ static void flush_pending_writes(struct r1conf *conf) * backgroup IO calls must call raise_barrier. Once that returns * there is no normal IO happeing. It must arrange to call * lower_barrier when the particular background IO completes. + * + * If resync/recovery is interrupted, returns -EINTR; + * Otherwise, returns 0. */ -static sector_t raise_barrier(struct r1conf *conf, sector_t sector_nr) +static int raise_barrier(struct r1conf *conf, sector_t sector_nr) { int idx = sector_to_idx(sector_nr);