Eric W. Biederman 5d5422a294 Revert 95ebabde382c ("capabilities: Don't allow writing ambiguous v3 file capabilities") ... commit 3b0c2d3eaa83da259d7726192cf55a137769012f upstream. It turns out that there are in fact userspace implementations that care and this recent change caused a regression. https://github.com/containers/buildah/issues/3071 As the motivation for the original change was future development, and the impact is existing real world code just revert this change and allow the ambiguity in v3 file caps. Cc: stable@vger.kernel.org Fixes: 95ebabde382c ("capabilities: Don't allow writing ambiguous v3 file capabilities") Signed-off-by: Eric W. Biederman <ebiederm@xmission.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2021-03-17 17:06:27 +01:00
..
apparmor
bpf
integrity	certs: Fix blacklist flag type confusion	2021-03-04 11:37:59 +01:00
keys	KEYS: trusted: Reserve TPM for seal and unseal operations	2021-03-04 11:38:29 +01:00
loadpin
lockdown
safesetid
selinux	selinux: fix inconsistency between inode_getxattr and inode_listsecurity	2021-03-04 11:38:28 +01:00
smack	smackfs: restrict bytes count in smackfs write functions	2021-03-07 12:34:05 +01:00
tomoyo	tomoyo: recognize kernel threads correctly	2021-03-09 11:11:15 +01:00
yama
commoncap.c	Revert 95ebabde382c ("capabilities: Don't allow writing ambiguous v3 file capabilities")	2021-03-17 17:06:27 +01:00
device_cgroup.c
inode.c
Kconfig
Kconfig.hardening
lsm_audit.c	dump_common_audit_data(): fix racy accesses to ->d_name	2021-01-19 18:27:29 +01:00
Makefile
min_addr.c
security.c