From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Borislav Petkov <bp@alien8.de>, Tejun Heo <tj@kernel.org>,
Tejun Heo <htejun@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: WARNING: at kernel/lockdep.c:690 __lock_acquire+0x168/0x164b()
Date: Sun, 16 Oct 2011 08:09:20 +0300 [thread overview]
Message-ID: <20111016050920.GB3475@swordfish> (raw)
In-Reply-To: <alpine.DEB.2.00.1110151529570.25063@chino.kir.corp.google.com>
On (10/15/11 15:32), David Rientjes wrote:
> > > I think this is a problem with lockdep itself, could you try reverting
> > > f59de8992aa6 ("lockdep: Clear whole lockdep_map on initialization") if
> > > this reliably happens everytime you reboot (lockdep will only emit this
> > > once and then will suppress future warnings until the next boot)?
> > >
> > > I think the new memset() is inadvertently clearing the name for
> > > double_unlock_balance().
> >
> > Great,
> >
> > so I'm not the only one seeing the above:
> > http://marc.info/?l=linux-kernel&m=131468805610527
> >
> > Due to it being very hard to reproduce, we dismissed it then as a
> > possible hw corruption.
> >
> > But yeah, it looks like I have triggered it on -rc9 too, just the
> > other day. Oh, and I see -rc6 and -rc8 warnings in the logs too. Ok,
> > correction, not that hard to trigger.
> >
>
> Could you try to revert f59de8992aa6 ("lockdep: Clear whole lockdep_map on
> initialization") with this patch and see if it helps? Thanks.
Sure, I'd love to and will do, it's just I'm not sure I can easily reproduce it.
> ---
> diff --git a/kernel/lockdep.c b/kernel/lockdep.c
> --- a/kernel/lockdep.c
> +++ b/kernel/lockdep.c
> @@ -2874,7 +2874,10 @@ static int mark_lock(struct task_struct *curr, struct held_lock *this,
> void lockdep_init_map(struct lockdep_map *lock, const char *name,
> struct lock_class_key *key, int subclass)
> {
> - memset(lock, 0, sizeof(*lock));
> + int i;
> +
> + for (i = 0; i < NR_LOCKDEP_CACHING_CLASSES; i++)
> + lock->class_cache[i] = NULL;
>
> #ifdef CONFIG_LOCK_STAT
> lock->cpu = raw_smp_processor_id();
>
next prev parent reply other threads:[~2011-10-16 5:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 20:12 WARNING: at kernel/lockdep.c:690 __lock_acquire+0x168/0x164b() Sergey Senozhatsky
2011-10-15 21:42 ` David Rientjes
2011-10-15 22:23 ` Borislav Petkov
2011-10-15 22:32 ` David Rientjes
2011-10-16 5:09 ` Sergey Senozhatsky [this message]
2011-10-20 18:39 ` Borislav Petkov
2011-10-20 18:53 ` Sergey Senozhatsky
2011-10-20 19:07 ` Sergey Senozhatsky
2011-10-20 21:17 ` David Rientjes
2011-10-20 21:23 ` Tejun Heo
2011-10-20 21:31 ` David Rientjes
2011-10-20 21:36 ` Tejun Heo
2011-10-20 23:00 ` Sergey Senozhatsky
2011-10-21 9:14 ` David Rientjes
2011-10-21 9:26 ` Sergey Senozhatsky
2011-10-21 9:45 ` Yong Zhang
2011-11-03 7:17 ` Sergey Senozhatsky
2011-11-03 7:27 ` Yong Zhang
2011-11-03 7:45 ` Sergey Senozhatsky
2011-11-03 7:53 ` Yong Zhang
2011-11-04 9:25 ` Borislav Petkov
2011-11-04 9:31 ` Sergey Senozhatsky
2011-11-07 4:54 ` Yong Zhang
2011-11-07 8:43 ` Sergey Senozhatsky
2011-11-04 9:34 ` Yong Zhang
2011-11-04 9:51 ` 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=20111016050920.GB3475@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=tj@kernel.org \
/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