From: Qian Cai <cai@lca.pw>
To: Bart Van Assche <bvanassche@acm.org>,
peterz@infradead.org, mingo@redhat.com, will.deacon@arm.com
Cc: longman@redhat.com, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] lockdep: skip debugobjects for lock_classes[] init
Date: Sun, 3 Mar 2019 22:06:27 -0500 [thread overview]
Message-ID: <59ac7210-03f5-99db-8ffd-47dbfc307709@lca.pw> (raw)
In-Reply-To: <c20aa0f0-42ab-a884-d931-7d4ec2bf0cdc@acm.org>
On 3/3/19 1:19 PM, Bart Van Assche wrote:
> [PATCH] locking/lockdep: Only call init_rcu_head() after RCU has been
> initialized
>
> init_data_structures_once() is called for the first time before RCU has
> been initialized. Make sure that init_rcu_head() is called before the
> RCU head is used and after RCU has been initialized.
>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
I like your approach more.
Tested-by: Qian Cai <cai@lca.pw>
next prev parent reply other threads:[~2019-03-04 3:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 4:02 [PATCH -next] lockdep: skip debugobjects for lock_classes[] init Qian Cai
2019-03-03 18:19 ` Bart Van Assche
2019-03-04 3:06 ` Qian Cai [this message]
2019-03-09 14:41 ` [tip:locking/urgent] locking/lockdep: Only call init_rcu_head() after RCU has been initialized tip-bot for Bart Van Assche
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=59ac7210-03f5-99db-8ffd-47dbfc307709@lca.pw \
--to=cai@lca.pw \
--cc=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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).