From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [xfs-linux:iomap-for-next 25/40] fs/iomap/direct-io.o: warning: objtool: __iomap_dio_rw()+0x849: unreachable instruction
Date: Fri, 20 Aug 2021 10:58:50 +0800 [thread overview]
Message-ID: <202108201042.DVGtmlWY-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1578 bytes --]
CC: linux-xfs(a)vger.kernel.org
TO: Christoph Hellwig <hch@lst.de>
CC: "Darrick J. Wong" <djwong@kernel.org>
tree: https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git iomap-for-next
head: 742dd4b8c5bbf1547c3090d42be76cb92a33feb1
commit: a6d3d49587d10d23189675fce11b332a915081ff [25/40] iomap: switch __iomap_dio_rw to use iomap_iter
config: x86_64-randconfig-a016-20210818 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project d2b574a4dea5b718e4386bf2e26af0126e5978ce)
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
# https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git/commit/?id=a6d3d49587d10d23189675fce11b332a915081ff
git remote add xfs-linux https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
git fetch --no-tags xfs-linux iomap-for-next
git checkout a6d3d49587d10d23189675fce11b332a915081ff
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross O=build_dir ARCH=x86_64 SHELL=/bin/bash fs/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> fs/iomap/direct-io.o: warning: objtool: __iomap_dio_rw()+0x849: unreachable instruction
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 32483 bytes --]
reply other threads:[~2021-08-20 2:58 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=202108201042.DVGtmlWY-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.