Linus Torvalds 028db3e290 Revert "Merge tag 'keys-acl-20190703' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs" ... This reverts merge 0f75ef6a9c (and thus effectively commits 7a1ade8475 ("keys: Provide KEYCTL_GRANT_PERMISSION") 2e12256b9a ("keys: Replace uid/gid/perm permissions checking with an ACL") that the merge brought in). It turns out that it breaks booting with an encrypted volume, and Eric biggers reports that it also breaks the fscrypt tests [1] and loading of in-kernel X.509 certificates [2]. The root cause of all the breakage is likely the same, but David Howells is off email so rather than try to work it out it's getting reverted in order to not impact the rest of the merge window. [1] https://lore.kernel.org/lkml/20190710011559.GA7973@sol.localdomain/ [2] https://lore.kernel.org/lkml/20190710013225.GB7973@sol.localdomain/ Link: https://lore.kernel.org/lkml/CAHk-=wjxoeMJfeBahnWH=9zShKp2bsVy527vo3_y8HfOdhwAAw@mail.gmail.com/ Reported-by: Eric Biggers <ebiggers@kernel.org> Cc: David Howells <dhowells@redhat.com> Cc: James Morris <jmorris@namei.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2019-07-10 18:43:43 -07:00
..
Kconfig	treewide: Add SPDX license identifier - Makefile/Kconfig	2019-05-21 10:50:46 +02:00
Makefile	treewide: Add SPDX license identifier - Makefile/Kconfig	2019-05-21 10:50:46 +02:00
bio.c	Clean up fscrypt's dcache revalidation support, and other	2019-05-07 21:28:04 -07:00
crypto.c	treewide: Add SPDX license identifier for more missed files	2019-05-21 10:50:45 +02:00
fname.c	fscrypt: fix race where ->lookup() marks plaintext dentry as ciphertext	2019-04-17 10:07:51 -04:00
fscrypt_private.h	fscrypt: remove filesystem specific build config option	2019-01-23 23:56:43 -05:00
hooks.c	treewide: Add SPDX license identifier for missed files	2019-05-21 10:50:45 +02:00
keyinfo.c	Revert "Merge tag 'keys-acl-20190703' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs"	2019-07-10 18:43:43 -07:00
policy.c	fscrypt: use READ_ONCE() to access ->i_crypt_info	2019-04-16 18:57:09 -04:00