public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [mark:stacktrace/tests 30/30] lib/stacktrace_kunit.c:901:40: error: use of undeclared identifier 'kp_addr'
Date: Thu, 6 Jun 2024 05:42:39 +0800	[thread overview]
Message-ID: <202406060529.9sHU462i-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git stacktrace/tests
head:   b355c7c11a4a1cec3478bc7a2f129638d9b5116d
commit: b355c7c11a4a1cec3478bc7a2f129638d9b5116d [30/30] WIP: lib: add more stacktracing tests
config: i386-buildonly-randconfig-005-20240606 (https://download.01.org/0day-ci/archive/20240606/202406060529.9sHU462i-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240606/202406060529.9sHU462i-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/202406060529.9sHU462i-lkp@intel.com/

All errors (new ones prefixed by >>):

>> lib/stacktrace_kunit.c:901:40: error: use of undeclared identifier 'kp_addr'
     901 |         kunit_info(test, "hit kprobe at %pS", kp_addr);
         |                                               ^
>> lib/stacktrace_kunit.c:901:40: error: use of undeclared identifier 'kp_addr'
   2 errors generated.


vim +/kp_addr +901 lib/stacktrace_kunit.c

   884	
   885	static void __do_test_one_async_kp(struct kunit *test,
   886					  callee_t callee,
   887					  const void *tracee,
   888					  kprobe_pre_handler_t kp_handler,
   889					  std_expect_t expect)
   890	{
   891		struct stacktrace_test_data *std = test->priv;
   892	
   893		if (!__do_kprobe_unwind(test, callee, tracee, kp_handler))
   894			return;
   895	
   896		if (!std->hit) {
   897			kunit_info(test, "did not hit kprobe at %pS", tracee);
   898			return;
   899		}
   900	
 > 901		kunit_info(test, "hit kprobe at %pS", kp_addr);
   902	
   903		expect(test, std);
   904	}
   905	

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

                 reply	other threads:[~2024-06-05 21:43 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=202406060529.9sHU462i-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox