From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, balbi@ti.com, tj@kernel.org,
serge.hallyn@canonical.com, jwboyer@fedoraproject.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [GIT PULL rcu/urgent] Fix regression from conversion to RCU_LOCKDEP_WARN()
Date: Sat, 12 Sep 2015 10:27:50 +0200 [thread overview]
Message-ID: <20150912082750.GA10942@gmail.com> (raw)
In-Reply-To: <20150909221607.GA26671@linux.vnet.ibm.com>
* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> Hello, Ingo,
>
> This additional series contains a single fix for a regression introduced
> earlier in this merge window:
>
> 1. security/device_cgroup: f78f5b90c4ff ("rcu: Rename
> rcu_lockdep_assert() to RCU_LOCKDEP_WARN()") introduced a
> bug by incorrectly inverting the condition when moving from
> rcu_lockdep_assert() to RCU_LOCKDEP_WARN(). This commit therefore
> fixes the inversion.
>
> This change has been subjected to 0day Test Robot and -next testing,
> and is available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git for-mingo
>
> for you to fetch changes up to dc3a04d551b5d21f1badbb39bfe8e5bc1289b184:
>
> security/device_cgroup: Fix RCU_LOCKDEP_WARN() condition (2015-09-03 18:13:10 -0700)
>
> ----------------------------------------------------------------
> Paul E. McKenney (1):
> security/device_cgroup: Fix RCU_LOCKDEP_WARN() condition
>
> security/device_cgroup.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Pulled, thanks a lot Paul!
Ingo
prev parent reply other threads:[~2015-09-12 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 22:16 [GIT PULL rcu/urgent] Fix regression from conversion to RCU_LOCKDEP_WARN() Paul E. McKenney
2015-09-12 8:27 ` Ingo Molnar [this message]
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=20150912082750.GA10942@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=balbi@ti.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=serge.hallyn@canonical.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