From: Ingo Molnar <mingo@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Sasha Levin <sasha.levin@oracle.com>
Cc: aryabinin@virtuozzo.com, krinkin.m.u@gmail.com, mingo@elte.hu,
peterz@infradead.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: + kernel-locking-lockdepc-make-lockdep-initialize-itself-on-demand.patch added to -mm tree
Date: Mon, 29 Feb 2016 10:11:02 +0100 [thread overview]
Message-ID: <20160229091102.GA8361@gmail.com> (raw)
In-Reply-To: <20160209121732.7713af6a1e244e1af00324de@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> wrote:
> On Tue, 9 Feb 2016 12:12:29 +0100 Ingo Molnar <mingo@kernel.org> wrote:
>
> > > The conceptual problem is that if some piece of code does spin_lock_init() or
> > > DEFINE_SPINLOCK(), that lock isn't necessarily initialized yet.
> >
> > The conceptual problem is that the data structures are not build time initialized
> > - but the hlist conversion patch solves that problem nicely!
> >
> > So I'm a happy camper.
>
> OK, so the below has been in -next for nearly a week, no issues. We
> should get this into 4.5 to fix the CONFIG_UBSAN_ALIGNMENT issue.
So I think this patch broke liblockdep:
triton:~/tip/tools/lib/lockdep>
In file included from lockdep.c:2:0:
../../../kernel/locking/lockdep.c: In function ‘look_up_lock_class’:
../../../kernel/locking/lockdep.c:722:2: warning: implicit declaration of function ‘hlist_for_each_entry_rcu’ [-Wimplicit-function-declaration]
hlist_for_each_entry_rcu(class, hash_head, hash_entry) {
...
Thanks,
Ingo
next prev parent reply other threads:[~2016-02-29 9:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56b11d2d.vVw1kB2la7Y+70xF%akpm@linux-foundation.org>
2016-02-03 7:44 ` + kernel-locking-lockdepc-make-lockdep-initialize-itself-on-demand.patch added to -mm tree Ingo Molnar
2016-02-03 9:42 ` Andrey Ryabinin
2016-02-03 9:49 ` Ingo Molnar
2016-02-03 16:51 ` Andrew Morton
2016-02-03 20:40 ` Andrew Morton
2016-02-03 21:44 ` Andrew Morton
2016-02-04 13:13 ` Andrey Ryabinin
2016-02-08 9:33 ` Michael Ellerman
2016-02-09 11:00 ` Ingo Molnar
2016-02-09 11:12 ` Ingo Molnar
2016-02-09 20:17 ` Andrew Morton
2016-02-29 9:11 ` Ingo Molnar [this message]
2016-02-29 9:25 ` Ingo Molnar
2016-02-29 9:30 ` Andrey Ryabinin
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=20160229091102.GA8361@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=krinkin.m.u@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sasha.levin@oracle.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).