]> git.baikalelectronics.ru Git - kernel.git/commit
block: bfq: fix bfq_set_next_ioprio_data()
authorDamien Le Moal <damien.lemoal@wdc.com>
Wed, 11 Aug 2021 03:36:57 +0000 (12:36 +0900)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 22 Sep 2021 10:26:21 +0000 (12:26 +0200)
commitb79912c66c15591554cd076ec53b3e7275a83c01
tree1e4aa4aed62046e25cc6246310b88c29d2e1de90
parent88adb7da07fe22b8d792d5ad2c81c640ac03b8e2
block: bfq: fix bfq_set_next_ioprio_data()

commit a680dd72ec336b81511e3bff48efac6dbfa563e7 upstream.

For a request that has a priority level equal to or larger than
IOPRIO_BE_NR, bfq_set_next_ioprio_data() prints a critical warning but
defaults to setting the request new_ioprio field to IOPRIO_BE_NR. This
is not consistent with the warning and the allowed values for priority
levels. Fix this by setting the request new_ioprio field to
IOPRIO_BE_NR - 1, the lowest priority level allowed.

Cc: <stable@vger.kernel.org>
Fixes: 2019a1bd9c10 ("block, bfq: introduce the BFQ-v0 I/O scheduler as an extra scheduler")
Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Link: https://lore.kernel.org/r/20210811033702.368488-2-damien.lemoal@wdc.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
block/bfq-iosched.c