On 07/06/2015 07:08 PM, Arianna Avanzini wrote:
Currently, per-blkcg data is freed each time a policy is deactivated,
that is also upon scheduler switch. However, when switching from a
scheduler implementing a policy which requires per-blkcg data to
another one, that same policy might be active on other devices, and
therefore those same per-blkcg data could be still in use.
This commit lets per-blkcg data be freed when the blkcg is freed
instead of on policy deactivation.
Signed-off-by: Arianna Avanzini <[email protected]>
Reported-and-tested-by: Michael Kaminsky <[email protected]>
Fixes: e48453c3 ("block, cgroup: implement policy-specific per-blkcg data")
Thanks Arianna, applied! Hopefully this is the end of the per-policy
data issues for 4.2.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
