From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jan Kara <jack@suse.cz>
Subject: Re: fs/reiserfs/inode.o: warning: objtool: reiserfs_write_folio+0x394: unreachable instruction
Date: Wed, 24 Jul 2024 02:03:07 +0100 [thread overview]
Message-ID: <ZqBSy1-kmS28JVH8@casper.infradead.org> (raw)
In-Reply-To: <202407240856.rcNo0xl1-lkp@intel.com>
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@intel.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.
next prev parent reply other threads:[~2024-07-24 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 0:56 kernel test robot
2024-07-24 1:03 ` Matthew Wilcox [this message]
2024-07-24 2:15 ` Philip Li
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=ZqBSy1-kmS28JVH8@casper.infradead.org \
--to=willy@infradead.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@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
all inboxes | Powered by JetHome®