From: Alexandre Chartre <alexandre.chartre@oracle.com>
To: kernel test robot <lkp@intel.com>
Cc: Chandan Babu R <chandanbabu@kernel.org>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
alexandre.chartre@oracle.com
Subject: Re: [linux-next:master 8491/8619] fs/xfs/xfs.o: warning: objtool: xfs_da_grow_inode_int+0x6c1: stack state mismatch: reg1[12]=-2-48 reg2[12]=-1+0
Date: Wed, 6 Mar 2024 10:42:36 +0100 [thread overview]
Message-ID: <Zeg6jCoQXSPlxvg0@laptop-dell-latitude7430.home> (raw)
In-Reply-To: <202402220435.MGN0EV6l-lkp@intel.com>
On Thu, Feb 22, 2024 at 04:30:01AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 4893c639cc3659cefaa675bf1e59f4e7571afb5c
> commit: 5954d6aa1b01ac362d88df2f34073cd23e819c89 [8491/8619] Merge branch 'for-next' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
> config: x86_64-randconfig-a016-20220509 (https://download.01.org/0day-ci/archive/20240222/202402220435.MGN0EV6l-lkp@intel.com/config)
> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240222/202402220435.MGN0EV6l-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/202402220435.MGN0EV6l-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> fs/xfs/xfs.o: warning: objtool: xfs_da_grow_inode_int+0x6c1: stack state mismatch: reg1[12]=-2-48 reg2[12]=-1+0
>
This is a problem with objtool which is confusing some addressing mode
and incorrectly thinks that a saved register has been restored. I am
working on a fix and I will submit an objtool patch (shortly hopefully).
Rgds,
alex.
prev parent reply other threads:[~2024-03-06 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 20:30 kernel test robot
2024-03-06 9:42 ` Alexandre Chartre [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=Zeg6jCoQXSPlxvg0@laptop-dell-latitude7430.home \
--to=alexandre.chartre@oracle.com \
--cc=chandanbabu@kernel.org \
--cc=linux-mm@kvack.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