summaryrefslogtreecommitdiffstats
path: root/init
diff options
context:
space:
mode:
authorPaolo Valente <paolo.valente@linaro.org>2021-11-25 19:15:10 +0100
committerJens Axboe <axboe@kernel.dk>2022-03-09 01:56:45 +0100
commit15729ff8143f8135b03988a100a19e66d7cb7ecd (patch)
tree0502944198cbf147772714c99d7fc483d06f0ae9 /init
parentblock: remove bio_devname (diff)
downloadlinux-15729ff8143f8135b03988a100a19e66d7cb7ecd.tar.xz
linux-15729ff8143f8135b03988a100a19e66d7cb7ecd.zip
Revert "Revert "block, bfq: honor already-setup queue merges""
A crash [1] happened to be triggered in conjunction with commit 2d52c58b9c9b ("block, bfq: honor already-setup queue merges"). The latter was then reverted by commit ebc69e897e17 ("Revert "block, bfq: honor already-setup queue merges""). Yet, the reverted commit was not the one introducing the bug. In fact, it actually triggered a UAF introduced by a different commit, and now fixed by commit d29bd41428cf ("block, bfq: reset last_bfqq_created on group change"). So, there is no point in keeping commit 2d52c58b9c9b ("block, bfq: honor already-setup queue merges") out. This commit restores it. [1] https://bugzilla.kernel.org/show_bug.cgi?id=214503 Reported-by: Holger Hoffstätte <holger@applied-asynchrony.com> Signed-off-by: Paolo Valente <paolo.valente@linaro.org> Link: https://lore.kernel.org/r/20211125181510.15004-1-paolo.valente@linaro.org Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions