From: kbuild test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Linux Memory Management List <linux-mm@kvack.org>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: [hnaz-linux-mm:master 377/435] fs/reiserfs/ibalance.o: warning: objtool: balance_internal()+0x1ab4: stack state mismatch: cfa1=7+304 cfa2=7+328
Date: Wed, 25 Mar 2020 09:02:25 +0800 [thread overview]
Message-ID: <202003250903.e4rKVUTA%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
tree: https://github.com/hnaz/linux-mm master
head: a5cc37b1c84e9e7041328cc962d0eeb745b5a794
commit: a0b7476566f69163ca18260beb90f0531f78d231 [377/435] linux-next-rejects
config: x86_64-randconfig-b002-20200324 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project b6ae8937e031cde2e70e6a83d46c21e940fdf4ac)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout a0b7476566f69163ca18260beb90f0531f78d231
# save the attached .config to linux build tree
COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> fs/reiserfs/ibalance.o: warning: objtool: balance_internal()+0x1ab4: stack state mismatch: cfa1=7+304 cfa2=7+328
>> fs/reiserfs/ibalance.o: warning: objtool: internal_insert_key()+0x26b: stack state mismatch: cfa1=7+96 cfa2=7+112
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 47968 bytes --]
reply other threads:[~2020-03-25 1:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202003250903.e4rKVUTA%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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