From: kernel test robot <lkp@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org
Subject: [kees:for-next/kspp 12/12] fs/gfs2/meta_io.h:44:12: error: casting from randomized structure pointer type 'struct address_space *' to 'struct gfs2_glock *'
Date: Wed, 4 May 2022 15:32:27 +0800 [thread overview]
Message-ID: <202205041550.naKxwCBj-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/kspp
head: 1fe35f29cf8220a5f9ab39ee3e5c722eb716b6fa
commit: 1fe35f29cf8220a5f9ab39ee3e5c722eb716b6fa [12/12] randstruct: Enable Clang support
config: riscv-randconfig-c006-20220501 (https://download.01.org/0day-ci/archive/20220504/202205041550.naKxwCBj-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 363b3a645a1e30011cc8da624f13dac5fd915628)
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 riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?id=1fe35f29cf8220a5f9ab39ee3e5c722eb716b6fa
git remote add kees https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
git fetch --no-tags kees for-next/kspp
git checkout 1fe35f29cf8220a5f9ab39ee3e5c722eb716b6fa
# 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=riscv SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from fs/gfs2/acl.c:23:
>> fs/gfs2/meta_io.h:44:12: error: casting from randomized structure pointer type 'struct address_space *' to 'struct gfs2_glock *'
return (((struct gfs2_glock *)mapping) - 1)->gl_name.ln_sbd;
^
1 error generated.
vim +44 fs/gfs2/meta_io.h
009d851837ab26 Steven Whitehouse 2009-12-08 39
009d851837ab26 Steven Whitehouse 2009-12-08 40 static inline struct gfs2_sbd *gfs2_mapping2sbd(struct address_space *mapping)
009d851837ab26 Steven Whitehouse 2009-12-08 41 {
009d851837ab26 Steven Whitehouse 2009-12-08 42 struct inode *inode = mapping->host;
009d851837ab26 Steven Whitehouse 2009-12-08 43 if (mapping->a_ops == &gfs2_meta_aops)
15562c439d0a18 Bob Peterson 2015-03-16 @44 return (((struct gfs2_glock *)mapping) - 1)->gl_name.ln_sbd;
1b2ad41214c9bf Steven Whitehouse 2014-03-31 45 else if (mapping->a_ops == &gfs2_rgrp_aops)
1b2ad41214c9bf Steven Whitehouse 2014-03-31 46 return container_of(mapping, struct gfs2_sbd, sd_aspace);
009d851837ab26 Steven Whitehouse 2009-12-08 47 else
009d851837ab26 Steven Whitehouse 2009-12-08 48 return inode->i_sb->s_fs_info;
009d851837ab26 Steven Whitehouse 2009-12-08 49 }
b3b94faa5fe596 David Teigland 2006-01-16 50
:::::: The code at line 44 was first introduced by commit
:::::: 15562c439d0a1850b71aa1c0d92d1f4fb9503c8d GFS2: Move glock superblock pointer to field gl_name
:::::: TO: Bob Peterson <rpeterso@redhat.com>
:::::: CC: Bob Peterson <rpeterso@redhat.com>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-04 7:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202205041550.naKxwCBj-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).