linux-kernel - [GIT PULL rcu/urgent] Fix regression from conversion to RCU_LOCKDEP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 Sep 2015 15:16:07 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	mingo@...nel.org
Cc:	linux-kernel@...r.kernel.org, balbi@...com, tj@...nel.org,
	serge.hallyn@...onical.com, jwboyer@...oraproject.org
Subject: [GIT PULL rcu/urgent] Fix regression from conversion to
 RCU_LOCKDEP_WARN()

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(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/