summaryrefslogtreecommitdiff
path: root/drivers/md/raid1.c
diff options
context:
space:
mode:
authorYufen Yu <yuyufen@huawei.com>2019-01-29 16:34:04 +0800
committerJens Axboe <axboe@kernel.dk>2019-02-12 09:13:18 -0700
commit96d7cb932e826219ec41ac02e5af037ffae6098c (patch)
tree5064e8614989c7d577066c3d3a691b86f95fe864 /drivers/md/raid1.c
parentaef1897cd36dcf5e296f1d2bae7e0d268561b685 (diff)
floppy: check_events callback should not return a negative number
floppy_check_events() is supposed to return bit flags to say which events occured. We should return zero to say that no event flags are set. Only BIT(0) and BIT(1) are used in the caller. And .check_events interface also expect to return an unsigned int value. However, after commit a0c80efe5956, it may return -EINTR (-4u). Here, both BIT(0) and BIT(1) are cleared. So this patch shouldn't affect runtime, but it obviously is still worth fixing. Reviewed-by: Dan Carpenter <dan.carpenter@oracle.com> Fixes: a0c80efe5956 ("floppy: fix lock_fdc() signal handling") Signed-off-by: Yufen Yu <yuyufen@huawei.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/md/raid1.c')
0 files changed, 0 insertions, 0 deletions