diff options
author | 2012-01-12 02:16:06 +0000 | |
---|---|---|
committer | 2012-01-12 12:27:59 -0800 | |
commit | 1398eee08222a038fa5f017900f387e81f6e3ff4 (patch) | |
tree | 0ac3e3645b2a71d4c67471ef0c072cfd87c6ff48 /drivers/i2c/algos/i2c-algo-bit.c | |
parent | net: reintroduce missing rcu_assign_pointer() calls (diff) | |
download | wireguard-linux-1398eee08222a038fa5f017900f387e81f6e3ff4.tar.xz wireguard-linux-1398eee08222a038fa5f017900f387e81f6e3ff4.zip |
net: decrement memcg jump label when limit, not usage, is changed
The logic of the current code is that whenever we destroy
a cgroup that had its limit set (set meaning different than
maximum), we should decrement the jump_label counter.
Otherwise we assume it was never incremented.
But what the code actually does is test for RES_USAGE
instead of RES_LIMIT. Usage being different than maximum
is likely to be true most of the time.
The effect of this is that the key must become negative,
and since the jump_label test says:
!!atomic_read(&key->enabled);
we'll have jump_labels still on when no one else is
using this functionality.
Signed-off-by: Glauber Costa <glommer@parallels.com>
CC: David S. Miller <davem@davemloft.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/i2c/algos/i2c-algo-bit.c')
0 files changed, 0 insertions, 0 deletions