diff options
author | Carlo Nonato <carlo.nonato95@gmail.com> | 2020-03-06 13:27:31 +0100 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2020-03-06 07:00:58 -0700 |
commit | 14afc59361976c0ba39e3a9589c3eaa43ebc7e1d (patch) | |
tree | 96d75a33a683364150e29b0cc0f65483578bbada /include | |
parent | 153031a301bb07194e9c37466cfce8eacb977621 (diff) | |
download | linux-stable-14afc59361976c0ba39e3a9589c3eaa43ebc7e1d.tar.gz linux-stable-14afc59361976c0ba39e3a9589c3eaa43ebc7e1d.tar.bz2 linux-stable-14afc59361976c0ba39e3a9589c3eaa43ebc7e1d.zip |
block, bfq: fix overwrite of bfq_group pointer in bfq_find_set_group()
The bfq_find_set_group() function takes as input a blkcg (which represents
a cgroup) and retrieves the corresponding bfq_group, then it updates the
bfq internal group hierarchy (see comments inside the function for why
this is needed) and finally it returns the bfq_group.
In the hierarchy update cycle, the pointer holding the correct bfq_group
that has to be returned is mistakenly used to traverse the hierarchy
bottom to top, meaning that in each iteration it gets overwritten with the
parent of the current group. Since the update cycle stops at root's
children (depth = 2), the overwrite becomes a problem only if the blkcg
describes a cgroup at a hierarchy level deeper than that (depth > 2). In
this case the root's child that happens to be also an ancestor of the
correct bfq_group is returned. The main consequence is that processes
contained in a cgroup at depth greater than 2 are wrongly placed in the
group described above by BFQ.
This commits fixes this problem by using a different bfq_group pointer in
the update cycle in order to avoid the overwrite of the variable holding
the original group reference.
Reported-by: Kwon Je Oh <kwonje.oh2@gmail.com>
Signed-off-by: Carlo Nonato <carlo.nonato95@gmail.com>
Signed-off-by: Paolo Valente <paolo.valente@linaro.org>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions