mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@vger.kernel.org, mhiramat@kernel.org,
	"Jose E. Marchesi" <jose.marchesi@oracle.com>,
	Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH] tracepoint: Fix CFI failures with tp_stub_func
Date: Thu, 23 Mar 2023 12:26:50 -0400	[thread overview]
Message-ID: <20230323122650.5a1f2db7@gandalf.local.home> (raw)
In-Reply-To: <20230323085321.0f8d1b98@gandalf.local.home>

On Thu, 23 Mar 2023 08:53:21 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> > --- a/include/linux/tracepoint.h
> > +++ b/include/linux/tracepoint.h
> > @@ -303,6 +303,7 @@ static inline struct tracepoint *tracepoint_ptr_deref(tracepoint_ptr_t *p)
> >  	__section("__tracepoints_strings") = #_name;			\
> >  	extern struct static_call_key STATIC_CALL_KEY(tp_func_##_name);	\
> >  	int __traceiter_##_name(void *__data, proto);			\
> > +	void __tracestub_##_name(void *, proto);			\
> >  	struct tracepoint __tracepoint_##_name	__used			\
> >  	__section("__tracepoints") = {					\
> >  		.name = __tpstrtab_##_name,				\
> > @@ -310,6 +311,7 @@ static inline struct tracepoint *tracepoint_ptr_deref(tracepoint_ptr_t *p)
> >  		.static_call_key = &STATIC_CALL_KEY(tp_func_##_name),	\
> >  		.static_call_tramp = STATIC_CALL_TRAMP_ADDR(tp_func_##_name), \
> >  		.iterator = &__traceiter_##_name,			\
> > +		.stub = &__tracestub_##_name,				\
> >  		.regfunc = _reg,					\
> >  		.unregfunc = _unreg,					\
> >  		.funcs = NULL };					\
> > @@ -330,6 +332,9 @@ static inline struct tracepoint *tracepoint_ptr_deref(tracepoint_ptr_t *p)
> >  		}							\
> >  		return 0;						\
> >  	}								\
> > +	void __tracestub_##_name(void *__data, proto)			\
> > +	{								\
> > +	}								\  
> 
> I purposely did not do this because this adds over a thousand stub
> functions! It adds one for *every* tracepoint (and that is a superset of
> trace events).

And the commit that added this code:

  befe6d946551 ("tracepoint: Do not fail unregistering a probe due to memory failure")

Has this in the change log:

    [ Note, this version does use undefined compiler behavior (assuming that
      a stub function with no parameters or return, can be called by a location
      that thinks it has parameters but still no return value. Static calls
      do the same thing, so this trick is not without precedent.

      There's another solution that uses RCU tricks and is more complex, but
      can be an alternative if this solution becomes an issue.

      Link: https://lore.kernel.org/lkml/20210127170721.58bce7cc@gandalf.local.home/
    ]

-- Steve

  parent reply	other threads:[~2023-03-23 16:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 11:40 Mark Rutland
2023-03-23 12:53 ` Steven Rostedt
2023-03-23 13:45   ` Mark Rutland
2023-03-23 16:27     ` Mark Rutland
2023-03-23 16:34       ` Steven Rostedt
2023-03-23 18:37         ` Mathieu Desnoyers
2023-03-23 18:42           ` Steven Rostedt
2023-03-23 18:44             ` Mathieu Desnoyers
2023-03-23 16:26   ` Steven Rostedt [this message]
2023-03-23 16:32     ` Mark Rutland

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=20230323122650.5a1f2db7@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=jose.marchesi@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=ndesaulniers@google.com \
    /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®