llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [tglx-devel:rseq/wip 22/22] kernel/rseq.c:209:2: error: call to undeclared function 'trace_rseq_exit_to_user'; ISO C99 and later do not support implicit function declarations
Date: Mon, 18 Aug 2025 02:19:25 +0200	[thread overview]
Message-ID: <202508180201.8e33QEIl-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git rseq/wip
head:   302da1e6bb83bae8c47388b029ed29811455ddec
commit: 302da1e6bb83bae8c47388b029ed29811455ddec [22/22] rewrite
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250818/202508180201.8e33QEIl-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250818/202508180201.8e33QEIl-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/202508180201.8e33QEIl-lkp@intel.com/

All errors (new ones prefixed by >>):

>> kernel/rseq.c:209:2: error: call to undeclared function 'trace_rseq_exit_to_user'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     209 |         trace_rseq_exit_to_user(current);
         |         ^
   kernel/rseq.c:209:2: note: did you mean 'trace_seq_to_user'?
   include/linux/trace_seq.h:94:12: note: 'trace_seq_to_user' declared here
      94 | extern int trace_seq_to_user(struct trace_seq *s, char __user *ubuf,
         |            ^
   1 error generated.


vim +/trace_rseq_exit_to_user +209 kernel/rseq.c

   204	
   205	void __rseq_handle_slowpath(struct pt_regs *regs)
   206	{
   207		rseq_stat_inc(rseq_stats.slowp);
   208	
 > 209		trace_rseq_exit_to_user(current);
   210	
   211		// FIXME: Do something sensible here
   212		if (WARN_ON_ONCE(!regs))
   213			return;
   214	
   215		/*
   216		 * If fatal is true, then the fastpath found invalid data. No point
   217		 * in trying again and wasting cycles to get to the same
   218		 * conclusion.
   219		 */
   220		if (!current->rseq_event.fatal)
   221			rseq_slowpath_update_usr(regs, 0);
   222		else
   223			force_sig(SIGSEGV);
   224	}
   225	

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

                 reply	other threads:[~2025-08-18  0:19 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=202508180201.8e33QEIl-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tglx@linutronix.de \
    /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).