[01/15] fs, fscrypt: only define ->s_cop when FS_ENCRYPTION is enabled
diff mbox

Message ID 20180430225149.183514-2-ebiggers3@gmail.com
State Accepted
Headers show

Commit Message

Eric Biggers April 30, 2018, 10:51 p.m. UTC
From: Eric Biggers <ebiggers@google.com>

Now that filesystems only set and use their fscrypt_operations when they
are built with encryption support, we can remove ->s_cop from
'struct super_block' when FS_ENCRYPTION is disabled.  This saves a few
bytes on some kernels and also makes it consistent with ->i_crypt_info.

Signed-off-by: Eric Biggers <ebiggers@google.com>
 include/linux/fs.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff mbox

diff --git a/include/linux/fs.h b/include/linux/fs.h
index 760d8da1b6c7..8e2460694c3a 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -1364,9 +1364,9 @@  struct super_block {
 	void                    *s_security;
 	const struct xattr_handler **s_xattr;
 	const struct fscrypt_operations	*s_cop;
 	struct hlist_bl_head	s_roots;	/* alternate root dentries for NFS */
 	struct list_head	s_mounts;	/* list of mounts; _not_ for fs use */
 	struct block_device	*s_bdev;