Locking rules for fscrypt_operations->set_context()

From	Richard Weinberger <richard@nod.at>
Newsgroups	linux.kernel
Subject	Locking rules for fscrypt_operations->set_context()
Date	2016-09-20 16:40 +0200
Message-ID	<sjung-49Y-3@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View raw

Hi!

To my understanding ->setxattr() is always being called with i_mutex held.
->set_context() in ext4 stores the security context using ext4_xattr_set(),
but the fs crypto framework does not lock the inode itself.
So, depending on the call path, ext4_xattr_set() is sometimes being
called with i_mutex held and some times not.

What are the locking rules for fscrypt_operations and especially ->set_context()?

Thanks,
//richard

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Locking rules for fscrypt_operations->set_context() Richard Weinberger <richard@nod.at> - 2016-09-20 16:40 +0200
  Re: Locking rules for fscrypt_operations->set_context() Eric Biggers <ebiggers@google.com> - 2016-09-22 02:20 +0200

csiph-web