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,
On Fri, 2014-06-13 at 14:26 +0400, Denis Kirjanov wrote:
On 6/13/14, Catalin Marinas catalin.mari...@arm.com wrote:
On Fri, Jun 13, 2014 at 08:12:08AM +0100, Denis Kirjanov wrote:
On 6/12/14, Catalin Marinas catalin.mari...@arm.com wrote:
On Thu, Jun 12, 2014 at 01:00:57PM +0100, Denis
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
On 13 Jun 2014, at 22:44, Benjamin Herrenschmidt b...@kernel.crashing.org
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
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,
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
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
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 6/12/14, Naoya Horiguchi n-horigu...@ah.jp.nec.com wrote:
Hi Denis,
On Thu, Jun 12, 2014 at 04:00:57PM +0400, Denis Kirjanov wrote:
On 6/12/14, Denis Kirjanov k...@linux-powerpc.org wrote:
On 6/12/14, Catalin Marinas catalin.mari...@arm.com wrote:
On 11 Jun 2014, at 21:04, Denis
On 6/12/14, Catalin Marinas catalin.mari...@arm.com wrote:
On Thu, Jun 12, 2014 at 01:00:57PM +0100, Denis Kirjanov wrote:
On 6/12/14, Denis Kirjanov k...@linux-powerpc.org wrote:
On 6/12/14, Catalin Marinas catalin.mari...@arm.com wrote:
On 11 Jun 2014, at 21:04, Denis Kirjanov
On Fri, Jun 13, 2014 at 08:12:08AM +0100, Denis Kirjanov wrote:
On 6/12/14, Catalin Marinas catalin.mari...@arm.com wrote:
On Thu, Jun 12, 2014 at 01:00:57PM +0100, Denis Kirjanov wrote:
On 6/12/14, Denis Kirjanov k...@linux-powerpc.org wrote:
On 6/12/14, Catalin Marinas
On 6/13/14, Catalin Marinas catalin.mari...@arm.com wrote:
On Fri, Jun 13, 2014 at 08:12:08AM +0100, Denis Kirjanov wrote:
On 6/12/14, Catalin Marinas catalin.mari...@arm.com wrote:
On Thu, Jun 12, 2014 at 01:00:57PM +0100, Denis Kirjanov wrote:
On 6/12/14, Denis Kirjanov
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,
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
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 6/12/14, Catalin Marinas catalin.mari...@arm.com wrote:
On 11 Jun 2014, at 21:04, Denis Kirjanov k...@linux-powerpc.org wrote:
On 6/11/14, Catalin Marinas catalin.mari...@arm.com wrote:
On Wed, Jun 11, 2014 at 04:13:07PM +0400, Denis Kirjanov wrote:
I got a trace while running
On 6/12/14, Denis Kirjanov k...@linux-powerpc.org wrote:
On 6/12/14, Catalin Marinas catalin.mari...@arm.com wrote:
On 11 Jun 2014, at 21:04, Denis Kirjanov k...@linux-powerpc.org wrote:
On 6/11/14, Catalin Marinas catalin.mari...@arm.com wrote:
On Wed, Jun 11, 2014 at 04:13:07PM +0400, Denis
On Thu, Jun 12, 2014 at 01:00:57PM +0100, Denis Kirjanov wrote:
On 6/12/14, Denis Kirjanov k...@linux-powerpc.org wrote:
On 6/12/14, Catalin Marinas catalin.mari...@arm.com wrote:
On 11 Jun 2014, at 21:04, Denis Kirjanov k...@linux-powerpc.org wrote:
On 6/11/14, 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
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
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
Hi,
I got a trace while running 3.15.0-08556-gdfb9454:
[ 104.534026] Unable to handle kernel paging request for data at
address 0xc0007f00
[ 104.534197] Faulting instruction address: 0xc019cb50
[ 104.534204] Oops: Kernel access of bad area, sig: 11 [#1]
[ 104.534891] PREEMPT
Hi,
I got a trace while running 3.15.0-08556-gdfb9454:
[ 104.534026] Unable to handle kernel paging request for data at
address 0xc0007f00
[ 104.534197] Faulting instruction address: 0xc019cb50
[ 104.534204] Oops: Kernel access of bad area, sig: 11 [#1]
[ 104.534891] PREEMPT
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 could
On 6/11/14, Catalin Marinas catalin.mari...@arm.com 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
On 11 Jun 2014, at 21:04, Denis Kirjanov k...@linux-powerpc.org wrote:
On 6/11/14, Catalin Marinas catalin.mari...@arm.com 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
28 matches
Mail list logo