[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-24 Thread Qixuan Wu
On Sat, Sep 23, 2017, Yang Shi wrote: > > Kernel may panic when oom happens without killable process sometimes it > is caused by huge unreclaimable slabs used by kernel. > > Although kdump could help debug such problem, however, kdump is not > available on all

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-24 Thread Qixuan Wu
On Sat, Sep 23, 2017, Yang Shi wrote: > > Kernel may panic when oom happens without killable process sometimes it > is caused by huge unreclaimable slabs used by kernel. > > Although kdump could help debug such problem, however, kdump is not > available on all architectures and it might be

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-22 Thread Yang Shi
Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Although kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-22 Thread Yang Shi
Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Although kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-21 Thread Yang Shi
Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Although kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-21 Thread Yang Shi
Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Although kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-21 Thread Yang Shi
On 9/21/17 1:23 AM, David Rientjes wrote: On Thu, 21 Sep 2017, Yang Shi wrote: Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Although kdump could help debug such problem, however, kdump is not available on all

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-21 Thread Yang Shi
On 9/21/17 1:23 AM, David Rientjes wrote: On Thu, 21 Sep 2017, Yang Shi wrote: Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Although kdump could help debug such problem, however, kdump is not available on all

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-21 Thread David Rientjes
On Thu, 21 Sep 2017, Yang Shi wrote: > Kernel may panic when oom happens without killable process sometimes it > is caused by huge unreclaimable slabs used by kernel. > > Although kdump could help debug such problem, however, kdump is not > available on all architectures and it might be

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-21 Thread David Rientjes
On Thu, 21 Sep 2017, Yang Shi wrote: > Kernel may panic when oom happens without killable process sometimes it > is caused by huge unreclaimable slabs used by kernel. > > Although kdump could help debug such problem, however, kdump is not > available on all architectures and it might be

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-20 Thread Yang Shi
Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Although kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-20 Thread Yang Shi
Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Although kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-20 Thread Yang Shi
On 9/20/17 2:00 PM, David Rientjes wrote: On Thu, 21 Sep 2017, Yang Shi wrote: diff --git a/mm/oom_kill.c b/mm/oom_kill.c index 99736e0..173c423 100644 --- a/mm/oom_kill.c +++ b/mm/oom_kill.c @@ -43,6 +43,7 @@ #include #include "internal.h" +#include "slab.h" #define

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-20 Thread Yang Shi
On 9/20/17 2:00 PM, David Rientjes wrote: On Thu, 21 Sep 2017, Yang Shi wrote: diff --git a/mm/oom_kill.c b/mm/oom_kill.c index 99736e0..173c423 100644 --- a/mm/oom_kill.c +++ b/mm/oom_kill.c @@ -43,6 +43,7 @@ #include #include "internal.h" +#include "slab.h" #define

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-20 Thread David Rientjes
On Thu, 21 Sep 2017, Yang Shi wrote: > diff --git a/mm/oom_kill.c b/mm/oom_kill.c > index 99736e0..173c423 100644 > --- a/mm/oom_kill.c > +++ b/mm/oom_kill.c > @@ -43,6 +43,7 @@ > > #include > #include "internal.h" > +#include "slab.h" > > #define CREATE_TRACE_POINTS > #include > @@

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-20 Thread David Rientjes
On Thu, 21 Sep 2017, Yang Shi wrote: > diff --git a/mm/oom_kill.c b/mm/oom_kill.c > index 99736e0..173c423 100644 > --- a/mm/oom_kill.c > +++ b/mm/oom_kill.c > @@ -43,6 +43,7 @@ > > #include > #include "internal.h" > +#include "slab.h" > > #define CREATE_TRACE_POINTS > #include > @@

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-20 Thread Yang Shi
Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Altough kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-20 Thread Yang Shi
Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Altough kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-19 Thread Yang Shi
On 9/19/17 3:41 PM, David Rientjes wrote: On Wed, 20 Sep 2017, Yang Shi wrote: --- a/mm/slab_common.c +++ b/mm/slab_common.c @@ -35,6 +35,8 @@ static DECLARE_WORK(slab_caches_to_rcu_destroy_work, slab_caches_to_rcu_destroy_workfn); +#define K(x) ((x)/1024) + /*

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-19 Thread Yang Shi
On 9/19/17 3:41 PM, David Rientjes wrote: On Wed, 20 Sep 2017, Yang Shi wrote: --- a/mm/slab_common.c +++ b/mm/slab_common.c @@ -35,6 +35,8 @@ static DECLARE_WORK(slab_caches_to_rcu_destroy_work, slab_caches_to_rcu_destroy_workfn); +#define K(x) ((x)/1024) + /*

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-19 Thread David Rientjes
On Wed, 20 Sep 2017, Yang Shi wrote: > > > --- a/mm/slab_common.c > > > +++ b/mm/slab_common.c > > > @@ -35,6 +35,8 @@ > > > static DECLARE_WORK(slab_caches_to_rcu_destroy_work, > > > slab_caches_to_rcu_destroy_workfn); > > > +#define K(x) ((x)/1024) > > > + > > > /* >

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-19 Thread David Rientjes
On Wed, 20 Sep 2017, Yang Shi wrote: > > > --- a/mm/slab_common.c > > > +++ b/mm/slab_common.c > > > @@ -35,6 +35,8 @@ > > > static DECLARE_WORK(slab_caches_to_rcu_destroy_work, > > > slab_caches_to_rcu_destroy_workfn); > > > +#define K(x) ((x)/1024) > > > + > > > /* >

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-19 Thread Yang Shi
On 9/19/17 1:57 PM, David Rientjes wrote: On Tue, 19 Sep 2017, Yang Shi wrote: --- a/mm/slab_common.c +++ b/mm/slab_common.c @@ -35,6 +35,8 @@ static DECLARE_WORK(slab_caches_to_rcu_destroy_work, slab_caches_to_rcu_destroy_workfn); +#define K(x) ((x)/1024) + /*

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-19 Thread Yang Shi
On 9/19/17 1:57 PM, David Rientjes wrote: On Tue, 19 Sep 2017, Yang Shi wrote: --- a/mm/slab_common.c +++ b/mm/slab_common.c @@ -35,6 +35,8 @@ static DECLARE_WORK(slab_caches_to_rcu_destroy_work, slab_caches_to_rcu_destroy_workfn); +#define K(x) ((x)/1024) + /*

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-19 Thread David Rientjes
On Tue, 19 Sep 2017, Yang Shi wrote: > --- a/mm/slab_common.c > +++ b/mm/slab_common.c > @@ -35,6 +35,8 @@ > static DECLARE_WORK(slab_caches_to_rcu_destroy_work, > slab_caches_to_rcu_destroy_workfn); > > +#define K(x) ((x)/1024) > + > /* > * Set of flags that will prevent

Re: [PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-19 Thread David Rientjes
On Tue, 19 Sep 2017, Yang Shi wrote: > --- a/mm/slab_common.c > +++ b/mm/slab_common.c > @@ -35,6 +35,8 @@ > static DECLARE_WORK(slab_caches_to_rcu_destroy_work, > slab_caches_to_rcu_destroy_workfn); > > +#define K(x) ((x)/1024) > + > /* > * Set of flags that will prevent

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-18 Thread Yang Shi
Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Altough kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-18 Thread Yang Shi
Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Altough kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-18 Thread Yang Shi
Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Altough kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it

[PATCH 2/2] mm: oom: show unreclaimable slab info when kernel panic

2017-09-18 Thread Yang Shi
Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Altough kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it