diff options
author | Paolo Valente <[email protected]> | 2021-11-25 19:15:10 +0100 |
---|---|---|
committer | Jens Axboe <[email protected]> | 2022-03-08 17:56:45 -0700 |
commit | 15729ff8143f8135b03988a100a19e66d7cb7ecd (patch) | |
tree | 0502944198cbf147772714c99d7fc483d06f0ae9 /lib/mpi/mpi-sub-ui.c | |
parent | 97939610b893de068c82c347d06319cd231a4602 (diff) |
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 <[email protected]>
Signed-off-by: Paolo Valente <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'lib/mpi/mpi-sub-ui.c')
0 files changed, 0 insertions, 0 deletions