From: kernel test robot <lkp@intel.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, x86@kernel.org,
Peter Zijlstra <peterz@infradead.org>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>
Subject: [tip:perf/core 18/20] arch/x86/include/asm/unwind_user.h:16:12: error: no member named 'flags' in 'struct pt_regs'
Date: Wed, 29 Oct 2025 19:25:39 +0800 [thread overview]
Message-ID: <202510291919.FFGyU7nq-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
head: c69993ecdd4dfde2b7da08b022052a33b203da07
commit: 49cf34c0815f93fb2ea3ab5cfbac1124bd9b45d0 [18/20] unwind_user/x86: Enable frame pointer unwinding on x86
config: um-allnoconfig (https://download.01.org/0day-ci/archive/20251029/202510291919.FFGyU7nq-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project d1c086e82af239b245fe8d7832f2753436634990)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251029/202510291919.FFGyU7nq-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/202510291919.FFGyU7nq-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/fork.c:108:
In file included from include/linux/unwind_deferred.h:6:
In file included from include/linux/unwind_user.h:6:
>> arch/x86/include/asm/unwind_user.h:16:12: error: no member named 'flags' in 'struct pt_regs'
16 | if (regs->flags & X86_VM_MASK)
| ~~~~ ^
>> arch/x86/include/asm/unwind_user.h:16:20: error: use of undeclared identifier 'X86_VM_MASK'
16 | if (regs->flags & X86_VM_MASK)
| ^~~~~~~~~~~
2 errors generated.
vim +16 arch/x86/include/asm/unwind_user.h
6
7 #define ARCH_INIT_USER_FP_FRAME(ws) \
8 .cfa_off = 2*(ws), \
9 .ra_off = -1*(ws), \
10 .fp_off = -2*(ws), \
11 .use_fp = true,
12
13 static inline int unwind_user_word_size(struct pt_regs *regs)
14 {
15 /* We can't unwind VM86 stacks */
> 16 if (regs->flags & X86_VM_MASK)
17 return 0;
18 #ifdef CONFIG_X86_64
19 if (!user_64bit_mode(regs))
20 return sizeof(int);
21 #endif
22 return sizeof(long);
23 }
24
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-10-29 11:26 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=202510291919.FFGyU7nq-lkp@intel.com \
--to=lkp@intel.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=x86@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®