Re: [PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-30 Thread Shakeel Butt
On Tue, Oct 30, 2018 at 8:56 AM Roman Gushchin wrote: > > On Tue, Oct 30, 2018 at 07:12:49AM +0100, Michal Hocko wrote: > > On Mon 29-10-18 21:51:55, Roman Gushchin wrote: > > > Mike Galbraith reported a regression caused by the commit 9b6f7e163cd0 > > > ("mm: rework memcg kernel stack

Re: [PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-30 Thread Shakeel Butt
On Tue, Oct 30, 2018 at 8:56 AM Roman Gushchin wrote: > > On Tue, Oct 30, 2018 at 07:12:49AM +0100, Michal Hocko wrote: > > On Mon 29-10-18 21:51:55, Roman Gushchin wrote: > > > Mike Galbraith reported a regression caused by the commit 9b6f7e163cd0 > > > ("mm: rework memcg kernel stack

Re: [PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-30 Thread Roman Gushchin
On Tue, Oct 30, 2018 at 07:12:49AM +0100, Michal Hocko wrote: > On Mon 29-10-18 21:51:55, Roman Gushchin wrote: > > Mike Galbraith reported a regression caused by the commit 9b6f7e163cd0 > > ("mm: rework memcg kernel stack accounting") on a system with > > "cgroup_disable=memory" boot option: the

Re: [PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-30 Thread Roman Gushchin
On Tue, Oct 30, 2018 at 07:12:49AM +0100, Michal Hocko wrote: > On Mon 29-10-18 21:51:55, Roman Gushchin wrote: > > Mike Galbraith reported a regression caused by the commit 9b6f7e163cd0 > > ("mm: rework memcg kernel stack accounting") on a system with > > "cgroup_disable=memory" boot option: the

Re: [PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-30 Thread Michal Hocko
On Mon 29-10-18 21:51:55, Roman Gushchin wrote: > Mike Galbraith reported a regression caused by the commit 9b6f7e163cd0 > ("mm: rework memcg kernel stack accounting") on a system with > "cgroup_disable=memory" boot option: the system panics with the > following stack trace: > > [0.928542] BUG:

Re: [PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-30 Thread Michal Hocko
On Mon 29-10-18 21:51:55, Roman Gushchin wrote: > Mike Galbraith reported a regression caused by the commit 9b6f7e163cd0 > ("mm: rework memcg kernel stack accounting") on a system with > "cgroup_disable=memory" boot option: the system panics with the > following stack trace: > > [0.928542] BUG:

Re: [PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-29 Thread Shakeel Butt
On Mon, Oct 29, 2018 at 6:01 PM Rik van Riel wrote: > > On Mon, 2018-10-29 at 17:50 -0700, Shakeel Butt wrote: > > On Mon, Oct 29, 2018 at 2:52 PM Roman Gushchin wrote: > > > > > > Mike Galbraith reported a regression caused by the commit > > > 9b6f7e163cd0 > > > ("mm: rework memcg kernel stack

Re: [PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-29 Thread Shakeel Butt
On Mon, Oct 29, 2018 at 6:01 PM Rik van Riel wrote: > > On Mon, 2018-10-29 at 17:50 -0700, Shakeel Butt wrote: > > On Mon, Oct 29, 2018 at 2:52 PM Roman Gushchin wrote: > > > > > > Mike Galbraith reported a regression caused by the commit > > > 9b6f7e163cd0 > > > ("mm: rework memcg kernel stack

Re: [PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-29 Thread Rik van Riel
On Mon, 2018-10-29 at 17:50 -0700, Shakeel Butt wrote: > On Mon, Oct 29, 2018 at 2:52 PM Roman Gushchin wrote: > > > > Mike Galbraith reported a regression caused by the commit > > 9b6f7e163cd0 > > ("mm: rework memcg kernel stack accounting") on a system with > > "cgroup_disable=memory" boot

Re: [PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-29 Thread Rik van Riel
On Mon, 2018-10-29 at 17:50 -0700, Shakeel Butt wrote: > On Mon, Oct 29, 2018 at 2:52 PM Roman Gushchin wrote: > > > > Mike Galbraith reported a regression caused by the commit > > 9b6f7e163cd0 > > ("mm: rework memcg kernel stack accounting") on a system with > > "cgroup_disable=memory" boot

Re: [PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-29 Thread Shakeel Butt
On Mon, Oct 29, 2018 at 2:52 PM Roman Gushchin wrote: > > Mike Galbraith reported a regression caused by the commit 9b6f7e163cd0 > ("mm: rework memcg kernel stack accounting") on a system with > "cgroup_disable=memory" boot option: the system panics with the > following stack trace: > >

Re: [PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-29 Thread Shakeel Butt
On Mon, Oct 29, 2018 at 2:52 PM Roman Gushchin wrote: > > Mike Galbraith reported a regression caused by the commit 9b6f7e163cd0 > ("mm: rework memcg kernel stack accounting") on a system with > "cgroup_disable=memory" boot option: the system panics with the > following stack trace: > >

[PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-29 Thread Roman Gushchin
Mike Galbraith reported a regression caused by the commit 9b6f7e163cd0 ("mm: rework memcg kernel stack accounting") on a system with "cgroup_disable=memory" boot option: the system panics with the following stack trace: [0.928542] BUG: unable to handle kernel NULL pointer dereference at

[PATCH] mm: handle no memcg case in memcg_kmem_charge() properly

2018-10-29 Thread Roman Gushchin
Mike Galbraith reported a regression caused by the commit 9b6f7e163cd0 ("mm: rework memcg kernel stack accounting") on a system with "cgroup_disable=memory" boot option: the system panics with the following stack trace: [0.928542] BUG: unable to handle kernel NULL pointer dereference at