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
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
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
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:
>> >
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
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
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:
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
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:
>
>>
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
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
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
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
13 matches
Mail list logo