tree:   https://github.com/kdave/btrfs-devel.git ext/sweettea/fscrypt-v3
head:   4303e47e934b3af3940fbccf09515645b7084d78
commit: de4776dc6c651dbecf3aa4f8225aac3bf98e7690 [27/46] fscrypt: add extent-based encryption
config: arm-randconfig-c002-20221019
compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 791a7ae1ba3efd6bca96338e10ffde557ba83920)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install arm cross compiling tool for clang build
        # apt-get install binutils-arm-linux-gnueabi
        # https://github.com/kdave/btrfs-devel/commit/de4776dc6c651dbecf3aa4f8225aac3bf98e7690
        git remote add kdave-btrfs-devel https://github.com/kdave/btrfs-devel.git
        git fetch --no-tags kdave-btrfs-devel ext/sweettea/fscrypt-v3
        git checkout de4776dc6c651dbecf3aa4f8225aac3bf98e7690
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash fs/

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

   In file included from fs/crypto/crypto.c:29:
>> fs/crypto/fscrypt_private.h:307:19: warning: field iv within 'struct fscrypt_extent_context_v1' is less aligned than 'union fscrypt_iv' and is usually due to 'struct fscrypt_extent_context_v1' being packed, which can lead to unaligned accesses [-Wunaligned-access]
           union fscrypt_iv iv;
                            ^
   1 warning generated.


vim +307 fs/crypto/fscrypt_private.h

   294	
   295	
   296	/*
   297	 * fscrypt_extent_context - the encryption context for an extent
   298	 *
   299	 * For filesystems that support extent encryption, this context provides the
   300	 * necessary randomly-initialized IV in order to encrypt/decrypt the data
   301	 * stored in the extent. It is stored alongside each extent, and is
   302	 * insufficient to decrypt the extent: the extent's owning inode(s) provide the
   303	 * policy information (including key identifier) necessary to decrypt.
   304	 */
   305	struct fscrypt_extent_context_v1 {
   306		u8 version;
 > 307		union fscrypt_iv iv;
   308	} __packed;
   309	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp