mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
	oe-kbuild@lists.linux.dev,
	"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
	lkp@intel.com, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: kernel/trace/fgraph.c:834 __ftrace_return_to_handler() error: we previously assumed 'fregs' could be null (see line 830)
Date: Mon, 5 Jan 2026 11:13:55 +0900	[thread overview]
Message-ID: <20260105111355.47965a0e4d52b0ffdc102330@kernel.org> (raw)
In-Reply-To: <20260102120913.15e5fc1b@gandalf.local.home>

On Fri, 2 Jan 2026 12:09:13 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Fri, 2 Jan 2026 17:49:39 +0300
> Dan Carpenter <dan.carpenter@linaro.org> wrote:
> 
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head:   a919610db43b34621d0c3b333e12db9002caf5da
> > commit: 2ca8c112c9676e2394d76760db78ffddf21d93b5 fgraph: Pass ftrace_regs to retfunc
> > config: arm64-randconfig-r073-20251212 (https://download.01.org/0day-ci/archive/20251213/202512131657.JQUt5fXQ-lkp@intel.com/config)
> > compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 1335a05ab8bc8339ce24be3a9da89d8c3f4e0571)
> > 
> > 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>
> > | Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> > | Closes: https://lore.kernel.org/r/202512131657.JQUt5fXQ-lkp@intel.com/
> > 
> > smatch warnings:
> > kernel/trace/fgraph.c:834 __ftrace_return_to_handler() error: we previously assumed 'fregs' could be null (see line 830)
> > 
> > vim +/fregs +834 kernel/trace/fgraph.c
> > 
> > a3ed4157b7d898 Masami Hiramatsu (Google  2024-12-26  810) static inline unsigned long
> > a3ed4157b7d898 Masami Hiramatsu (Google  2024-12-26  811) __ftrace_return_to_handler(struct ftrace_regs *fregs, unsigned long frame_pointer)
> > d864a3ca883095 Steven Rostedt (VMware    2018-11-12  812) {
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  813) 	struct ftrace_ret_stack *ret_stack;
> > d864a3ca883095 Steven Rostedt (VMware    2018-11-12  814) 	struct ftrace_graph_ret trace;
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  815) 	unsigned long bitmap;
> > d864a3ca883095 Steven Rostedt (VMware    2018-11-12  816) 	unsigned long ret;
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  817) 	int offset;
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  818) 	int i;
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  819) 
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  820) 	ret_stack = ftrace_pop_return_trace(&trace, &ret, frame_pointer, &offset);
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  821) 
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  822) 	if (unlikely(!ret_stack)) {
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  823) 		ftrace_graph_stop();
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  824) 		WARN_ON(1);
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  825) 		/* Might as well panic. What else to do? */
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  826) 		return (unsigned long)panic;
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  827) 	}
> > d864a3ca883095 Steven Rostedt (VMware    2018-11-12  828) 
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  829) 	trace.rettime = trace_clock_local();
> > 2ca8c112c9676e Masami Hiramatsu (Google  2024-12-26 @830) 	if (fregs)
> > 
> > It's strange that Smatch is only now complaining about something which
> > is from 2024...  This line assumes "freqs" can be NULL.
> 
> Hmm, OK, I can see why smatch is complaining. But it is missing a dependency.
> 
> This is called by:
> 
> #ifdef CONFIG_HAVE_FUNCTION_GRAPH_FREGS
> unsigned long ftrace_return_to_handler(struct ftrace_regs *fregs)
> {
> 	return __ftrace_return_to_handler(fregs,
> 				ftrace_regs_get_frame_pointer(fregs));
> }
> #else
> unsigned long ftrace_return_to_handler(unsigned long frame_pointer)
> {
> 	return __ftrace_return_to_handler(NULL, frame_pointer);
> }
> #endif
> 
> Where if HAVE_FUNCTION_GRAPH_FREGS is true, then fregs is always set.
> 
> > 
> > 2ca8c112c9676e Masami Hiramatsu (Google  2024-12-26  831) 		ftrace_regs_set_instruction_pointer(fregs, ret);
> > 2ca8c112c9676e Masami Hiramatsu (Google  2024-12-26  832) 
> > a1be9ccc57f07d Donglin Peng              2023-04-08  833  #ifdef CONFIG_FUNCTION_GRAPH_RETVAL
> > a3ed4157b7d898 Masami Hiramatsu (Google  2024-12-26 @834) 	trace.retval = ftrace_regs_get_return_value(fregs);
> >                                                                                                             ^^^^^
> > Unchecked dereference.
> 
> Here FUNCTION_GRAPH_RETVAL has this in the Kconfig:
> 
> config FUNCTION_GRAPH_RETVAL
> 	bool "Kernel Function Graph Return Value"
> 	depends on HAVE_FUNCTION_GRAPH_FREGS
> 
> It depends on HAVE_FUNCTION_GRAPH_FREGS
> 
> Thus, it can't be called without fregs being valid.
> 
> Ideas on how to tell smatch about this?
> 
> Hmm, I wonder if we could change this to:
> 
> 	/* fregs is always set when configured */
> 	if (IS_ENABLED(CONFIG_HAVE_FUNCTION_GRAPH_FREGS))
> 		ftrace_regs_set_instruction_pointer(fregs, ret);
> 
> And also add:
> 
> #ifdef CONFIG_FUNCTION_GRAPH_RETVAL
> 	/* The below is always true, but makes smatch happy */
> 	if (IS_ENABLED(CONFIG_HAVE_FUNCTION_GRAPH_FREGS))
> 		trace.retval = ftrace_regs_get_return_value(fregs);
> #endif
> 
> ?

Can smatch understand fregs is not NULL if the
CONFIG_HAVE_FUNCTION_GRAPH_FREGS=y? If it can, I think this
can skip unneeded NULL pointer check at runtime.

(Or, define those macros to do nothing if CONFIG_HAVE_FUNCTION_GRAPH_FREGS=n)

Thank you,

> 
> -- Steve
> 
> 
> 
> > 
> > a1be9ccc57f07d Donglin Peng              2023-04-08  835  #endif
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  836) 
> > 7aa1eaef9f4282 Steven Rostedt (VMware    2024-06-03  837) 	bitmap = get_bitmap_bits(current, offset);
> > 420e1354bcb6f0 Steven Rostedt (Google    2024-06-03  838) 
> > 
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2026-01-05  2:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02 14:49 Dan Carpenter
2026-01-02 17:09 ` Steven Rostedt
2026-01-05  2:13   ` Masami Hiramatsu [this message]
2026-01-05 15:15     ` Dan Carpenter
2026-01-05 15:23       ` Steven Rostedt

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=20260105111355.47965a0e4d52b0ffdc102330@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=oe-kbuild@lists.linux.dev \
    --cc=rostedt@goodmis.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®