All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [mark:arm64/stacktrace/kunwind 1/2] arch/arm64/kernel/stacktrace.c:117:42: error: 'struct kunwind_state' has no member named 'pc'
Date: Thu, 9 Nov 2023 06:54:53 +0800	[thread overview]
Message-ID: <202311090655.NIPmhCSC-lkp@intel.com> (raw)

Hi Mark,

FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git arm64/stacktrace/kunwind
head:   73ada9012201d97bd158a87e5cc0cd0c2af7c20b
commit: d8a9a6ecc87ed6e6e2e0354e56239b415c1cec67 [1/2] arm64: stacktrace: factor out kernel unwind state
config: arm64-randconfig-004-20231108 (https://download.01.org/0day-ci/archive/20231109/202311090655.NIPmhCSC-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231109/202311090655.NIPmhCSC-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/202311090655.NIPmhCSC-lkp@intel.com/

All errors (new ones prefixed by >>):

   arch/arm64/kernel/stacktrace.c: In function 'kunwind_recover_return_address':
>> arch/arm64/kernel/stacktrace.c:117:42: error: 'struct kunwind_state' has no member named 'pc'
     117 |         if (is_kretprobe_trampoline(state->pc)) {
         |                                          ^~
   arch/arm64/kernel/stacktrace.c:118:22: error: 'struct kunwind_state' has no member named 'pc'
     118 |                 state->pc = kretprobe_find_ret_addr(state->task,
         |                      ^~
>> arch/arm64/kernel/stacktrace.c:119:66: error: 'struct kunwind_state' has no member named 'fp'
     119 |                                                     (void *)state->fp,
         |                                                                  ^~


vim +117 arch/arm64/kernel/stacktrace.c

9e09d445f1cab5 Mark Rutland 2023-04-11  115  
9e09d445f1cab5 Mark Rutland 2023-04-11  116  #ifdef CONFIG_KRETPROBES
9e09d445f1cab5 Mark Rutland 2023-04-11 @117  	if (is_kretprobe_trampoline(state->pc)) {
9e09d445f1cab5 Mark Rutland 2023-04-11  118  		state->pc = kretprobe_find_ret_addr(state->task,
9e09d445f1cab5 Mark Rutland 2023-04-11 @119  						    (void *)state->fp,
9e09d445f1cab5 Mark Rutland 2023-04-11  120  						    &state->kr_cur);
9e09d445f1cab5 Mark Rutland 2023-04-11  121  	}
9e09d445f1cab5 Mark Rutland 2023-04-11  122  #endif /* CONFIG_KRETPROBES */
9e09d445f1cab5 Mark Rutland 2023-04-11  123  
9e09d445f1cab5 Mark Rutland 2023-04-11  124  	return 0;
9e09d445f1cab5 Mark Rutland 2023-04-11  125  }
9e09d445f1cab5 Mark Rutland 2023-04-11  126  

:::::: The code at line 117 was first introduced by commit
:::::: 9e09d445f1cab518eedf4454d119ead27979b8f4 arm64: stacktrace: recover return address for first entry

:::::: TO: Mark Rutland <mark.rutland@arm.com>
:::::: CC: Will Deacon <will@kernel.org>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2023-11-08 22:55 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=202311090655.NIPmhCSC-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=mark.rutland@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.