Re: kmemleak: Unable to handle kernel paging request

2014-06-15 Thread Michael Ellerman
On Fri, 2014-06-13 at 14:26 +0400, Denis Kirjanov wrote: > On 6/13/14, Catalin Marinas wrote: > > On Fri, Jun 13, 2014 at 08:12:08AM +0100, Denis Kirjanov wrote: > >> On 6/12/14, Catalin Marinas wrote: > >> > On Thu, Jun 12, 2014 at 01:00:57PM +0100, Denis Kirjanov wrote: > >> >> On 6/12/14, Deni

Re: kmemleak: Unable to handle kernel paging request

2014-06-14 Thread Catalin Marinas
On 13 Jun 2014, at 22:44, Benjamin Herrenschmidt wrote: > On Fri, 2014-06-13 at 09:56 +0100, Catalin Marinas wrote: > >> OK, so that's the DART table allocated via alloc_dart_table(). Is >> dart_tablebase removed from the kernel linear mapping after allocation? > > Yes. > >> If that's the case

Re: kmemleak: Unable to handle kernel paging request

2014-06-13 Thread Benjamin Herrenschmidt
On Fri, 2014-06-13 at 09:56 +0100, Catalin Marinas wrote: > OK, so that's the DART table allocated via alloc_dart_table(). Is > dart_tablebase removed from the kernel linear mapping after allocation? Yes. > If that's the case, we need to tell kmemleak to ignore this block (see > patch below, unt

Re: kmemleak: Unable to handle kernel paging request

2014-06-13 Thread Denis Kirjanov
On 6/13/14, Catalin Marinas wrote: > On Fri, Jun 13, 2014 at 08:12:08AM +0100, Denis Kirjanov wrote: >> On 6/12/14, Catalin Marinas wrote: >> > On Thu, Jun 12, 2014 at 01:00:57PM +0100, Denis Kirjanov wrote: >> >> On 6/12/14, Denis Kirjanov wrote: >> >> > On 6/12/14, Catalin Marinas wrote: >> >

Re: kmemleak: Unable to handle kernel paging request

2014-06-13 Thread Catalin Marinas
On Fri, Jun 13, 2014 at 08:12:08AM +0100, Denis Kirjanov wrote: > On 6/12/14, Catalin Marinas wrote: > > On Thu, Jun 12, 2014 at 01:00:57PM +0100, Denis Kirjanov wrote: > >> On 6/12/14, Denis Kirjanov wrote: > >> > On 6/12/14, Catalin Marinas wrote: > >> >> On 11 Jun 2014, at 21:04, Denis Kirjan

Re: kmemleak: Unable to handle kernel paging request

2014-06-13 Thread Denis Kirjanov
On 6/12/14, Catalin Marinas wrote: > On Thu, Jun 12, 2014 at 01:00:57PM +0100, Denis Kirjanov wrote: >> On 6/12/14, Denis Kirjanov wrote: >> > On 6/12/14, Catalin Marinas wrote: >> >> On 11 Jun 2014, at 21:04, Denis Kirjanov >> >> wrote: >> >>> On 6/11/14, Catalin Marinas wrote: >> On Wed

Re: kmemleak: Unable to handle kernel paging request

2014-06-12 Thread Denis Kirjanov
On 6/12/14, Naoya Horiguchi wrote: > Hi Denis, > > On Thu, Jun 12, 2014 at 04:00:57PM +0400, Denis Kirjanov wrote: >> On 6/12/14, Denis Kirjanov wrote: >> > On 6/12/14, Catalin Marinas wrote: >> >> On 11 Jun 2014, at 21:04, Denis Kirjanov >> >> wrote: >> >>> On 6/11/14, Catalin Marinas wrote:

Re: kmemleak: Unable to handle kernel paging request

2014-06-12 Thread Catalin Marinas
On Thu, Jun 12, 2014 at 01:00:57PM +0100, Denis Kirjanov wrote: > On 6/12/14, Denis Kirjanov wrote: > > On 6/12/14, Catalin Marinas wrote: > >> On 11 Jun 2014, at 21:04, Denis Kirjanov wrote: > >>> On 6/11/14, Catalin Marinas wrote: > On Wed, Jun 11, 2014 at 04:13:07PM +0400, Denis Kirjano

Re: kmemleak: Unable to handle kernel paging request

2014-06-12 Thread Denis Kirjanov
On 6/12/14, Denis Kirjanov wrote: > On 6/12/14, Catalin Marinas wrote: >> On 11 Jun 2014, at 21:04, Denis Kirjanov wrote: >>> On 6/11/14, Catalin Marinas wrote: On Wed, Jun 11, 2014 at 04:13:07PM +0400, Denis Kirjanov wrote: > I got a trace while running 3.15.0-08556-gdfb9454: > >>

Re: kmemleak: Unable to handle kernel paging request

2014-06-12 Thread Denis Kirjanov
On 6/12/14, Catalin Marinas wrote: > On 11 Jun 2014, at 21:04, Denis Kirjanov wrote: >> On 6/11/14, Catalin Marinas wrote: >>> On Wed, Jun 11, 2014 at 04:13:07PM +0400, Denis Kirjanov wrote: I got a trace while running 3.15.0-08556-gdfb9454: [ 104.534026] Unable to handle kernel

Re: kmemleak: Unable to handle kernel paging request

2014-06-11 Thread Catalin Marinas
On 11 Jun 2014, at 21:04, Denis Kirjanov wrote: > On 6/11/14, Catalin Marinas wrote: >> On Wed, Jun 11, 2014 at 04:13:07PM +0400, Denis Kirjanov wrote: >>> I got a trace while running 3.15.0-08556-gdfb9454: >>> >>> [ 104.534026] Unable to handle kernel paging request for data at >>> address 0xc

Re: kmemleak: Unable to handle kernel paging request

2014-06-11 Thread Denis Kirjanov
On 6/11/14, Catalin Marinas wrote: > On Wed, Jun 11, 2014 at 04:13:07PM +0400, Denis Kirjanov wrote: >> I got a trace while running 3.15.0-08556-gdfb9454: >> >> [ 104.534026] Unable to handle kernel paging request for data at >> address 0xc0007f00 > > Were there any kmemleak messages prio

Re: kmemleak: Unable to handle kernel paging request

2014-06-11 Thread Catalin Marinas
On Wed, Jun 11, 2014 at 04:13:07PM +0400, Denis Kirjanov wrote: > I got a trace while running 3.15.0-08556-gdfb9454: > > [ 104.534026] Unable to handle kernel paging request for data at > address 0xc0007f00 Were there any kmemleak messages prior to this, like "kmemleak disabled"? There c