in_interrupt() check includes "have BH disabled" case,
as result allocations called with disabled BH are not accounted to
proper memory cgroup.
https://jira.sw.ru/browse/PSBM-108292
Signed-off-by: Vasily Averin
---
include/linux/memcontrol.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(
The commit is pushed to "branch-rh7-3.10.0-1127.18.2.vz7.163.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-1127.18.2.vz7.163.32
-->
commit bdd0719de2dc72afa136ec5907aede4ab1db94cb
Author: Vasily Averin
Date: Mon Oct 5 10:36:38 2020 +0300
memcg:
in_interrupt() check includes "have BH disabled" case,
as result allocations called with disabled BH are not accounted to
proper memory cgroup.
https://jira.sw.ru/browse/PSBM-120694
Signed-off-by: Vasily Averin
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
The commit is pushed to "branch-rh8-4.18.0-193.6.3.vz8.4.x-ovz" and will appear
at https://src.openvz.org/scm/ovz/vzkernel.git
after rh8-4.18.0-193.6.3.vz8.4.11
-->
commit e9a22ab1de9d9904945a5ed4abbbc9dff1bef6b1
Author: Andrey Ryabinin
Date: Mon Oct 5 12:00:58 2020 +0300
mm/memcg: fix
The commit is pushed to "branch-rh8-4.18.0-193.6.3.vz8.4.x-ovz" and will appear
at https://src.openvz.org/scm/ovz/vzkernel.git
after rh8-4.18.0-193.6.3.vz8.4.11
-->
commit 6fd293dbf5518d786f325db3b0f352385795f4bf
Author: Andrey Ryabinin
Date: Mon Oct 5 12:00:58 2020 +0300
mm/memcg: rec
The commit is pushed to "branch-rh8-4.18.0-193.6.3.vz8.4.x-ovz" and will appear
at https://src.openvz.org/scm/ovz/vzkernel.git
after rh8-4.18.0-193.6.3.vz8.4.11
-->
commit 67a87abe411ef0fbea509e04c9115f23fbb072f2
Author: Andrey Ryabinin
Date: Mon Oct 5 13:18:40 2020 +0300
mm, memcg: ad
The commit is pushed to "branch-rh8-4.18.0-193.6.3.vz8.4.x-ovz" and will appear
at https://src.openvz.org/scm/ovz/vzkernel.git
after rh8-4.18.0-193.6.3.vz8.4.11
-->
commit 060218e7064c3f370b0a8f6bbe8017971c15a89d
Author: Vasily Averin
Date: Mon Oct 5 13:20:48 2020 +0300
memcg: fixes ac
Lockdep complains that after rq_repin_lock() the lock wasn't unpinned
before rq->lock release.
[ cut here ]
releasing a pinned lock
WARNING: CPU: 0 PID: 24 at kernel/locking/lockdep.c:4271
lock_release+0x939/0xee0
Call Trace:
_raw_spin_unlock+0x1c/0x30
load_balance+0x147
On 05.10.2020 15:36, Andrey Ryabinin wrote:
> Lockdep complains that after rq_repin_lock() the lock wasn't unpinned
> before rq->lock release.
>
> [ cut here ]
> releasing a pinned lock
> WARNING: CPU: 0 PID: 24 at kernel/locking/lockdep.c:4271
> lock_release+0x939/0xee0
>
__alloc_pages_slowpath relies on the direct reclaim and did_some_progress
as an indicator that it makes sense to retry allocation rather than
declaring OOM. shrink_zones checks if all zones reclaimable and if
shrink_zone didn't make any progress it prevents from a premature OOM
killer invocation by
Userspace may ask tun device to send packet with ridiculously
big header and trigger this:
[ cut here ]
WARNING: CPU: 1 PID: 15366 at mm/page_alloc.c:3548
__alloc_pages_nodemask+0x537/0x1200
order 19 >= 11, gfp 0x2044d0
Call Trace:
dump_stack+0x19/0x1b
__warn+0x1
11 matches
Mail list logo