mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "kernel test robot" <lkp@intel.com>,
	"Arnd Bergmann" <arnd@kernel.org>,
	reiserfs-devel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reiserfs: avoid objtool warning after panic
Date: Fri, 16 Dec 2022 09:00:16 +0100	[thread overview]
Message-ID: <9355f758-9d06-4de8-85f7-e6ad870e784b@app.fastmail.com> (raw)
In-Reply-To: <202212160636.H31oByti-lkp@intel.com>

On Thu, Dec 15, 2022, at 23:31, kernel test robot wrote:
> Hi Arnd,
>
> I love your patch! Perhaps something to improve:
>
> compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
> reproduce (this is a W=1 build):
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
>>> fs/reiserfs/namei.o: warning: objtool: reiserfs_rename+0x212: unreachable instruction
> --
>>> fs/reiserfs/ibalance.o: warning: objtool: balance_internal_when_delete+0x44c: unreachable instruction
> --
>>> fs/reiserfs/stree.o: warning: objtool: reiserfs_cut_from_item+0x17a: unreachable instruction
> --
>>> fs/reiserfs/journal.o: warning: objtool: do_journal_end+0x4af: unreachable instruction
> --
>>> fs/reiserfs/item_ops.o: warning: objtool: direntry_check_left+0x65: unreachable instruction

Ok, I'll have to revisit this one. I think I tried something similar
before and ran into the same problem but I though I had figured
it out this time.

The problem apparently is that the patch to shut up the objtool
warning with clang in turn adds a different objtool warning with
gcc...

    Arnd

  reply	other threads:[~2022-12-16  8:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 16:27 Arnd Bergmann
2022-12-15 22:31 ` kernel test robot
2022-12-16  8:00   ` Arnd Bergmann [this message]
2022-12-15 22:51 ` 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=9355f758-9d06-4de8-85f7-e6ad870e784b@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=reiserfs-devel@vger.kernel.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 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®