From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 5609/6439] fs/bcachefs/btree_update_interior.o: warning: objtool: bch2_trans_verify_not_unlocked+0x18: stack state mismatch: cfa1=3+0 cfa2=3+16
Date: Fri, 23 Aug 2024 20:55:39 +0800 [thread overview]
Message-ID: <202408232023.5uNZM4tR-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: c79c85875f1af04040fe4492ed94ce37ad729c4d
commit: e4076169e231fa4142d8126b1cb920bf55fd9a19 [5609/6439] bcachefs: Assert that we don't lock nodes when !trans->locked
config: loongarch-randconfig-001-20240823 (https://download.01.org/0day-ci/archive/20240823/202408232023.5uNZM4tR-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/20240823/202408232023.5uNZM4tR-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/202408232023.5uNZM4tR-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/bcachefs/btree_update_interior.o: warning: objtool: bch2_trans_verify_not_unlocked+0x18: stack state mismatch: cfa1=3+0 cfa2=3+16
objdump-func vmlinux.o bch2_trans_verify_not_unlocked:
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-08-23 12:56 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=202408232023.5uNZM4tR-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-mm@kvack.org \
--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;
as well as URLs for NNTP newsgroup(s).