Tetsuo Handa 1b32e6ea73 tomoyo: Suppress RCU warning at list_for_each_entry_rcu(). ... [ Upstream commit 6bd5ce6089 ] John Garry has reported that allmodconfig kernel on arm64 causes flood of "RCU-list traversed in non-reader section!!" warning. I don't know what change caused this warning, but this warning is safe because TOMOYO uses SRCU lock instead. Let's suppress this warning by explicitly telling that the caller is holding SRCU lock. Reported-and-tested-by: John Garry <john.garry@huawei.com> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> Signed-off-by: Sasha Levin <sashal@kernel.org>		2020-01-17 19:49:05 +01:00
..
apparmor	apparmor: fix aa_xattrs_match() may sleep while holding a RCU lock	2020-01-09 10:20:00 +01:00
integrity	integrity: remove pointless subdir-$(CONFIG_...)	2019-10-05 15:29:49 +09:00
keys	KEYS: trusted: correctly initialize digests and fix locking issue	2019-09-25 02:43:53 +03:00
loadpin	…
lockdown	efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN	2019-10-31 09:40:21 +01:00
safesetid	LSM: SafeSetID: Stop releasing uninitialized ruleset	2019-09-17 11:27:05 -07:00
selinux	selinux/stable-5.4 PR 20191007	2019-10-08 10:51:37 -07:00
smack	I have four patches for v5.4. Nothing is major. All but one are in	2019-09-23 14:25:45 -07:00
tomoyo	tomoyo: Suppress RCU warning at list_for_each_entry_rcu().	2020-01-17 19:49:05 +01:00
yama	…
Kconfig	Merge branch 'next-lockdown' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security	2019-09-28 08:14:15 -07:00
Kconfig.hardening	…
Makefile	…
commoncap.c	…
device_cgroup.c	…
inode.c	…
lsm_audit.c	…
min_addr.c	…
security.c	Merge branch 'next-lockdown' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security	2019-09-28 08:14:15 -07:00