[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZqBjzC1Zlfd3zG4P@rli9-mobl>
Date: Wed, 24 Jul 2024 10:15:40 +0800
From: Philip Li <philip.li@...el.com>
To: Matthew Wilcox <willy@...radead.org>
CC: kernel test robot <lkp@...el.com>, <oe-kbuild-all@...ts.linux.dev>,
<linux-kernel@...r.kernel.org>, Jan Kara <jack@...e.cz>
Subject: Re: fs/reiserfs/inode.o: warning: objtool:
reiserfs_write_folio+0x394: unreachable instruction
On Wed, Jul 24, 2024 at 02:03:07AM +0100, Matthew Wilcox wrote:
> On Wed, Jul 24, 2024 at 08:56:24AM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 5ad7ff8738b8bd238ca899df08badb1f61bcc39e
> > commit: 4f8cf60ac18bee62e8c58654a300eb44b96caf09 reiserfs: Convert to writepages
> > date: 3 months ago
> > config: loongarch-randconfig-001-20240722 (https://download.01.org/0day-ci/archive/20240724/202407240856.rcNo0xl1-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/20240724/202407240856.rcNo0xl1-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@...el.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202407240856.rcNo0xl1-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>):
> >
> > fs/reiserfs/inode.o: warning: objtool: restart_transaction+0x38: unreachable instruction
> > fs/reiserfs/inode.o: warning: objtool: reiserfs_write_begin+0x90: unreachable instruction
> > fs/reiserfs/inode.o: warning: objtool: __reiserfs_write_begin+0x88: unreachable instruction
> > >> fs/reiserfs/inode.o: warning: objtool: reiserfs_write_folio+0x394: unreachable instruction
> > fs/reiserfs/inode.o: warning: objtool: reiserfs_new_inode+0x8c: unreachable instruction
>
> I don't care. I doubt anyone cares. Either about loongarch or
> reiserfs.
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.
>
Powered by blists - more mailing lists