Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: kernel test robot <lkp@intel.com>,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	Eric Sandeen <sandeen@redhat.com>, Chao Yu <yuchao0@huawei.com>,
	Chao Yu <chao@kernel.org>
Subject: Re: [linux-next:master 10769/12889] vmlinux.o: warning: objtool: f2fs_parse_param+0x80: sibling call from callable instruction with modified stack frame
Date: Thu, 31 Jul 2025 10:58:20 -0700	[thread overview]
Message-ID: <20250731175820.GB1455142@ax162> (raw)
In-Reply-To: <ee3e9dfb-a5a9-4dd1-aaaf-916ed2938403@huawei.com>

On Thu, Jul 31, 2025 at 09:47:45AM +0800, Hongbo Li wrote:
> > > > vmlinux.o: warning: objtool: f2fs_parse_param+0x80: sibling call from callable instruction with modified stack frame
> 
> Does this need to be addressed? It appears to be related to compiler
> optimization settings.

I have started a separate thread with some LoongArch folks around this
issue:

https://lore.kernel.org/20250731175655.GA1455142@ax162/

Cheers,
Nathan

      reply	other threads:[~2025-07-31 17:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30 11:02 [linux-next:master 10769/12889] vmlinux.o: warning: objtool: f2fs_parse_param+0x80: sibling call from callable instruction with modified stack frame kernel test robot
2025-07-31  1:47 ` Hongbo Li
2025-07-31 17:58   ` Nathan Chancellor [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=20250731175820.GB1455142@ax162 \
    --to=nathan@kernel.org \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=lihongbo22@huawei.com \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sandeen@redhat.com \
    --cc=yuchao0@huawei.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