From: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, llvm@lists.linux.dev
Subject: [hch-block:block-file.c 2/2] block/bdev.o: warning: objtool: bd_prepare_to_claim()+0x16c: unreachable instruction
Date: Sun, 5 Sep 2021 20:04:49 +0800 [thread overview]
Message-ID: <202109052042.P9itSJyo-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
TO: Christoph Hellwig <hch@lst.de>
Hi Christoph,
First bad commit (maybe != root cause):
tree: git://git.infradead.org/users/hch/block.git block-file.c
head: 3bf9453cb432aa7a08192ed5d6bf99e4adee6105
commit: 3bf9453cb432aa7a08192ed5d6bf99e4adee6105 [2/2] block: move fs/block_dev.c to block/bdev.c
config: x86_64-randconfig-a001-20210905 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 6fe2beba7d2a41964af658c8c59dd172683ef739)
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
git remote add hch-block git://git.infradead.org/users/hch/block.git
git fetch --no-tags hch-block block-file.c
git checkout 3bf9453cb432aa7a08192ed5d6bf99e4adee6105
# 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
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 >>):
>> block/bdev.o: warning: objtool: bd_prepare_to_claim()+0x16c: unreachable instruction
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34909 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [hch-block:block-file.c 2/2] block/bdev.o: warning: objtool: bd_prepare_to_claim()+0x16c: unreachable instruction
Date: Sun, 05 Sep 2021 20:04:49 +0800 [thread overview]
Message-ID: <202109052042.P9itSJyo-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
TO: Christoph Hellwig <hch@lst.de>
Hi Christoph,
First bad commit (maybe != root cause):
tree: git://git.infradead.org/users/hch/block.git block-file.c
head: 3bf9453cb432aa7a08192ed5d6bf99e4adee6105
commit: 3bf9453cb432aa7a08192ed5d6bf99e4adee6105 [2/2] block: move fs/block_dev.c to block/bdev.c
config: x86_64-randconfig-a001-20210905 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 6fe2beba7d2a41964af658c8c59dd172683ef739)
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
git remote add hch-block git://git.infradead.org/users/hch/block.git
git fetch --no-tags hch-block block-file.c
git checkout 3bf9453cb432aa7a08192ed5d6bf99e4adee6105
# 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
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 >>):
>> block/bdev.o: warning: objtool: bd_prepare_to_claim()+0x16c: 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: 34909 bytes --]
next reply other threads:[~2021-09-05 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 12:04 kernel test robot [this message]
2021-09-05 12:04 ` [hch-block:block-file.c 2/2] block/bdev.o: warning: objtool: bd_prepare_to_claim()+0x16c: unreachable instruction kernel test robot
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=202109052042.P9itSJyo-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.