From: Sergey Senozhatsky <sergey.senozhatsky@mail.by>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Ingo Molnar <mingo@elte.hu>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: kmemleak not tainted
Date: Tue, 7 Jul 2009 14:51:28 +0300 [thread overview]
Message-ID: <20090707115128.GA3238@localdomain.by> (raw)
[-- Attachment #1: Type: text/plain, Size: 2328 bytes --]
Hello,
Just noticed:
kernel: [ 1917.133154] INFO: RCU detected CPU 0 stall (t=485140/3000 jiffies)
kernel: [ 1917.133154] Pid: 511, comm: kmemleak Not tainted 2.6.31-rc2-nv-git1-00254-ga4e2f0a-dirty #2
kernel: [ 1917.133154] Call Trace:
kernel: [ 1917.133154] [<c141784d>] ? printk+0x23/0x36
kernel: [ 1917.133154] [<c10a81e0>] __rcu_pending+0x140/0x210
kernel: [ 1917.133154] [<c10a82da>] rcu_pending+0x2a/0x70
kernel: [ 1917.133154] [<c1051b8f>] update_process_times+0x3f/0x80
kernel: [ 1917.133154] [<c107148f>] tick_sched_timer+0x6f/0xf0
kernel: [ 1917.133154] [<c10640a6>] __run_hrtimer+0x56/0xe0
kernel: [ 1917.133154] [<c1071420>] ? tick_sched_timer+0x0/0xf0
kernel: [ 1917.133154] [<c1071420>] ? tick_sched_timer+0x0/0xf0
kernel: [ 1917.133154] [<c1064aa5>] hrtimer_interrupt+0x145/0x270
kernel: [ 1917.133154] [<c101c48c>] smp_apic_timer_interrupt+0x5c/0xb0
kernel: [ 1917.133154] [<c12582b8>] ? trace_hardirqs_off_thunk+0xc/0x14
kernel: [ 1917.133154] [<c1003e36>] apic_timer_interrupt+0x36/0x3c
kernel: [ 1917.133154] [<c141ad61>] ? _read_unlock_irqrestore+0x41/0x70
kernel: [ 1917.133154] [<c10f7415>] find_and_get_object+0x75/0xe0
kernel: [ 1917.133154] [<c10f73a0>] ? find_and_get_object+0x0/0xe0
kernel: [ 1917.133154] [<c10f7577>] scan_block+0x87/0x110
kernel: [ 1917.133154] [<c10f7880>] kmemleak_scan+0x280/0x420
kernel: [ 1917.133154] [<c10f7600>] ? kmemleak_scan+0x0/0x420
kernel: [ 1917.133154] [<c10f80b0>] ? kmemleak_scan_thread+0x0/0xc0
kernel: [ 1917.133154] [<c10f8100>] kmemleak_scan_thread+0x50/0xc0
kernel: [ 1917.133154] [<c105ff54>] kthread+0x84/0x90
kernel: [ 1917.133154] [<c105fed0>] ? kthread+0x0/0x90
kernel: [ 1917.133154] [<c100401b>] kernel_thread_helper+0x7/0x1c
static struct kmemleak_object *find_and_get_object(unsigned long ptr, int alias)
{
unsigned long flags;
struct kmemleak_object *object = NULL;
rcu_read_lock();
read_lock_irqsave(&kmemleak_lock, flags);
if (ptr >= min_addr && ptr < max_addr)
object = lookup_object(ptr, alias);
>> read_unlock_irqrestore(&kmemleak_lock, flags);
/* check whether the object is still available */
if (object && !get_object(object))
object = NULL;
rcu_read_unlock();
return object;
}
I'm not sure where this is kmemleak's problem, since with 31 I see lots of 'not tainted' reports on my laptop.
Sergey
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 315 bytes --]
next reply other threads:[~2009-07-07 11:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 11:51 Sergey Senozhatsky [this message]
2009-07-07 12:47 ` Catalin Marinas
2009-07-07 13:17 ` Sergey Senozhatsky
2009-07-07 13:22 ` Catalin Marinas
2009-07-07 13:45 ` Sergey Senozhatsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090707115128.GA3238@localdomain.by \
--to=sergey.senozhatsky@mail.by \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penberg@cs.helsinki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox