Displaying 9 results from an estimated 9 matches for "oom_reaper".
2019 Sep 06
0
possible deadlock in __mmu_notifier_invalidate_range_end
...d99a03250fe1f at syzkaller.appspotmail.com
Fixes: e58b341134ca ("Merge remote-tracking branch 'hmm/hmm'")
============================================
WARNING: possible recursive locking detected
5.3.0-rc6-next-20190830 #75 Not tainted
--------------------------------------------
oom_reaper/1065 is trying to acquire lock:
ffffffff8904ff60 (mmu_notifier_invalidate_range_start){+.+.}, at:
__mmu_notifier_invalidate_range_end+0x0/0x360 mm/mmu_notifier.c:169
but task is already holding lock:
ffffffff8904ff60 (mmu_notifier_invalidate_range_start){+.+.}, at:
__oom_reap_task_mm+0x196/0x4...
2016 Jun 19
2
[RFC PATCH] vhost, mm: make sure that oom_reaper doesn't reap memory read by vhost
On Sat 18-06-16 03:09:02, Michael S. Tsirkin wrote:
> On Fri, Jun 17, 2016 at 11:00:17AM +0200, Michal Hocko wrote:
[...]
> > It seems that vhost usage would suffer from this problem because
> > it reads from the userspace to get (status) flags and makes some
> > decisions based on the read value. I do not understand the code so I
> > couldn't evaluate whether that
2016 Jun 19
2
[RFC PATCH] vhost, mm: make sure that oom_reaper doesn't reap memory read by vhost
On Sat 18-06-16 03:09:02, Michael S. Tsirkin wrote:
> On Fri, Jun 17, 2016 at 11:00:17AM +0200, Michal Hocko wrote:
[...]
> > It seems that vhost usage would suffer from this problem because
> > it reads from the userspace to get (status) flags and makes some
> > decisions based on the read value. I do not understand the code so I
> > couldn't evaluate whether that
2016 Jun 18
0
[RFC PATCH] vhost, mm: make sure that oom_reaper doesn't reap memory read by vhost
...the killed task context.
>
> Make sure that each place which can read from userspace is annotated
> properly and it uses copy_from_user_mm, __get_user_mm resp.
> copy_from_iter_mm. Each will get the target mm as an argument and it
> performs a pessimistic check to rule out that the oom_reaper could
> possibly unmap the particular page. __oom_reap_task then just needs to
> mark the mm as unstable before it unmaps any page.
>
> This is a preparatory patch without any functional changes because
> the oom reaper doesn't touch mm shared with kthreads yet.
>
> Signe...
2016 Jun 17
2
[RFC PATCH] vhost, mm: make sure that oom_reaper doesn't reap memory read by vhost
...cision visible
outside of the killed task context.
Make sure that each place which can read from userspace is annotated
properly and it uses copy_from_user_mm, __get_user_mm resp.
copy_from_iter_mm. Each will get the target mm as an argument and it
performs a pessimistic check to rule out that the oom_reaper could
possibly unmap the particular page. __oom_reap_task then just needs to
mark the mm as unstable before it unmaps any page.
This is a preparatory patch without any functional changes because
the oom reaper doesn't touch mm shared with kthreads yet.
Signed-off-by: Michal Hocko <mhocko a...
2016 Jun 17
2
[RFC PATCH] vhost, mm: make sure that oom_reaper doesn't reap memory read by vhost
...cision visible
outside of the killed task context.
Make sure that each place which can read from userspace is annotated
properly and it uses copy_from_user_mm, __get_user_mm resp.
copy_from_iter_mm. Each will get the target mm as an argument and it
performs a pessimistic check to rule out that the oom_reaper could
possibly unmap the particular page. __oom_reap_task then just needs to
mark the mm as unstable before it unmaps any page.
This is a preparatory patch without any functional changes because
the oom reaper doesn't touch mm shared with kthreads yet.
Signed-off-by: Michal Hocko <mhocko a...
2023 Jul 27
1
High memory consumption for small AXFR
..._memcg=/system.slice/system-nsd.slice/nsd at trial.service,task=nsd: server 1,pid=709906,uid=111
23:32:33 kernel: Out of memory: Killed process 709906 (nsd: server 1) total-vm:14673408kB, anon-rss:13054016kB, file-rss:0kB, shmem-rss:384kB, UID:111 pgtables:28720kB oom_score_adj:0
23:32:40 kernel: oom_reaper: reaped process 709906 (nsd: server 1), now anon-rss:0kB, file-rss:0kB, shmem-rss:512kB
23:32:40 kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/system-nsd.slice/nsd at trial.service,task=nsd: main,pid=635022,uid=111
23:32:40...
2019 Jul 12
2
Out of memory: kill process
...dding more Ram is not a solution. Perhaps is there some memory leak somewhere ?
Thanks
[762294.966826] Out of memory: Kill process 848 (samba) score 90 or sacrifice child
[762294.968147] Killed process 155556 (samba) total-vm:1142900kB, anon-rss:23484kB, file-rss:4kB, shmem-rss:0kB
[762294.976191] oom_reaper: reaped process 155556 (samba), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
[762303.508349] samba invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), nodemask=(null), order=0, oom_score_adj=0
[762303.508350] samba cpuset=/ mems_allowed=0
[762303.508355] CPU: 0 PID: 155555 Comm: samba Not...
2019 Jul 12
0
Out of memory: kill process
...s there some
> memory leak somewhere ?
> Thanks
>
> [762294.966826] Out of memory: Kill process 848 (samba) score
> 90 or sacrifice child
> [762294.968147] Killed process 155556 (samba)
> total-vm:1142900kB, anon-rss:23484kB, file-rss:4kB, shmem-rss:0kB
> [762294.976191] oom_reaper: reaped process 155556 (samba),
> now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
> [762303.508349] samba invoked oom-killer:
> gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), nodemask=(null),
> order=0, oom_score_adj=0
> [762303.508350] samba cpuset=/ mems_allowed=0
> [762303.508355] C...