From: Philip Li <philip.li@intel.com>
To: Qu Wenruo <wqu@suse.com>
Cc: kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
David Sterba <dsterba@suse.com>
Subject: Re: fs/btrfs/lzo.o: warning: objtool: lzo_compress_folios+0xb0: unreachable instruction
Date: Wed, 24 Jul 2024 10:36:43 +0800 [thread overview]
Message-ID: <ZqBou6g6iC7OLGZn@rli9-mobl> (raw)
In-Reply-To: <fbe7c1cd-ff4f-4252-baf2-88d3c5e50fdc@suse.com>
On Wed, Jul 24, 2024 at 11:45:42AM +0930, Qu Wenruo wrote:
>
>
> 在 2024/7/24 11:32, Philip Li 写道:
> > On Tue, Jul 23, 2024 at 08:18:41PM +0800, kernel test robot wrote:
> > > Hi Qu,
> > >
> > > FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
> > >
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > > head: 66ebbdfdeb093e097399b1883390079cd4c3022b
> > > commit: 400b172b8cdcff87038697169fe9e4222120dd9a btrfs: compression: migrate compression/decompression paths to folios
> > > date: 3 months ago
> > > config: loongarch-randconfig-001-20240722 (https://download.01.org/0day-ci/archive/20240723/202407232006.7Gelsbv4-lkp@intel.com/config)
> > > compiler: loongarch64-linux-gcc (GCC) 14.1.0
> > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240723/202407232006.7Gelsbv4-lkp@intel.com/reproduce)
> > >
> > > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > > the same patch/commit), kindly add following tags
> > > | Reported-by: kernel test robot <lkp@intel.com>
> > > | Closes: https://lore.kernel.org/oe-kbuild-all/202407232006.7Gelsbv4-lkp@intel.com/
> > >
> > > All warnings (new ones prefixed by >>):
> >
> > Sorry, kindly ignore this report which could be related to tool chain upgrade to
> > loongarch64-linux-gcc (GCC) 14.1.0.
> >
> > We will further check whether the issue can be reproduced on gcc-13.
>
> Gcc 14.1 is totally fine, as that's the version I'm using already (although
> a little newer, 14.1.1)
>
> It would be even better to focus on more common architectures first (x86_64,
> aarch64), and put a lower priority on less common architectures.
thanks for the suggestion, the bot covers all archs, for the case here,
the commit works fine on x86 or aarch64, and only triggers a bisected report
on loongarch. We will block such false positve report and do a comparison
check whether this specific issue can be reproduced on other compilers, though
we can not quickly tell whether this is toolchain issue or real issue.
>
> As most developers are not really able to access those platforms easily.
>
> Thanks,
> Qu
>
> >
> > >
> > > > > fs/btrfs/lzo.o: warning: objtool: lzo_compress_folios+0xb0: unreachable instruction
> > > fs/btrfs/lzo.o: warning: objtool: lzo_decompress_bio+0x140: unreachable instruction
> > >
> > >
> > > objdump-func vmlinux.o lzo_compress_folios:
> > >
> > > --
> > > 0-DAY CI Kernel Test Service
> > > https://github.com/intel/lkp-tests/wiki
> > >
prev parent reply other threads:[~2024-07-24 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 12:18 kernel test robot
2024-07-24 2:02 ` Philip Li
2024-07-24 2:15 ` Qu Wenruo
2024-07-24 2:36 ` Philip Li [this message]
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=ZqBou6g6iC7OLGZn@rli9-mobl \
--to=philip.li@intel.com \
--cc=dsterba@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wqu@suse.com \
/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
all inboxes | Powered by JetHome®