summaryrefslogtreecommitdiffstats
path: root/drivers/md/raid1.c
diff options
context:
space:
mode:
authorDan Carpenter <dan.carpenter@oracle.com>2019-06-26 11:42:51 +0200
committerSong Liu <songliubraving@fb.com>2019-06-26 21:18:48 +0200
commit16d4b74654ff7c3c5d0b6446278ef51b1de41484 (patch)
treea7cad43b003300fa4dd175b809fc982ced84a5dd /drivers/md/raid1.c
parentblock, bfq: re-schedule empty queues if they deserve I/O plugging (diff)
downloadlinux-16d4b74654ff7c3c5d0b6446278ef51b1de41484.tar.xz
linux-16d4b74654ff7c3c5d0b6446278ef51b1de41484.zip
md/raid1: Fix a warning message in remove_wb()
The WARN_ON() macro doesn't take an error message, it just takes a condition. I've changed this to use WARN(1, "...") instead. Fixes: 3e148a320979 ("md/raid1: fix potential data inconsistency issue with write behind device") Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Song Liu <songliubraving@fb.com>
Diffstat (limited to 'drivers/md/raid1.c')
-rw-r--r--drivers/md/raid1.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/md/raid1.c b/drivers/md/raid1.c
index 3d44da663797..34e26834ad28 100644
--- a/drivers/md/raid1.c
+++ b/drivers/md/raid1.c
@@ -96,7 +96,7 @@ static void remove_wb(struct md_rdev *rdev, sector_t lo, sector_t hi)
}
if (!found)
- WARN_ON("The write behind IO is not recorded\n");
+ WARN(1, "The write behind IO is not recorded\n");
spin_unlock_irqrestore(&rdev->wb_list_lock, flags);
wake_up(&rdev->wb_io_wait);
}