Commit 4675719d authored by Hou Tao's avatar Hou Tao Committed by Song Liu

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: default avatarHou Tao <houtao1@huawei.com>
Signed-off-by: default avatarSong Liu <songliubraving@fb.com>
parent 00ec4f30
...@@ -872,8 +872,11 @@ static void flush_pending_writes(struct r1conf *conf) ...@@ -872,8 +872,11 @@ static void flush_pending_writes(struct r1conf *conf)
* backgroup IO calls must call raise_barrier. Once that returns * backgroup IO calls must call raise_barrier. Once that returns
* there is no normal IO happeing. It must arrange to call * there is no normal IO happeing. It must arrange to call
* lower_barrier when the particular background IO completes. * 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); int idx = sector_to_idx(sector_nr);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment