All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yauheni Kaliuta <ykaliuta@redhat.com>
To: bpf@vger.kernel.org
Cc: andrii@kernel.org,  ast@kernel.org
Subject: Re: [PATCH] tracing: perf_call_bpf: use struct trace_entry in struct syscall_tp_t
Date: Thu, 27 Jul 2023 18:08:20 +0300	[thread overview]
Message-ID: <xunyzg3hpf2z.fsf@redhat.com> (raw)
In-Reply-To: <20230727150534.397532-1-ykaliuta@redhat.com> (Yauheni Kaliuta's message of "Thu, 27 Jul 2023 18:05:34 +0300")


Resending with proper subject.

>>>>> On Thu, 27 Jul 2023 18:05:34 +0300, Yauheni Kaliuta  wrote:

 > bpf tracepoint program uses struct trace_event_raw_sys_enter as
 > argument where trace_entry is the first field. Use the same instead
 > of unsigned long long since if it's amended (for example by RT
 > patch) it accesses data with wrong offset.

 > Signed-off-by: Yauheni Kaliuta <ykaliuta@redhat.com>
 > ---
 >  kernel/trace/trace_syscalls.c | 10 ++++++++--
 >  1 file changed, 8 insertions(+), 2 deletions(-)

 > diff --git a/kernel/trace/trace_syscalls.c b/kernel/trace/trace_syscalls.c
 > index 942ddbdace4a..07f4fa395e99 100644
 > --- a/kernel/trace/trace_syscalls.c
 > +++ b/kernel/trace/trace_syscalls.c
 > @@ -555,12 +555,15 @@ static int perf_call_bpf_enter(struct trace_event_call *call, struct pt_regs *re
 >  			       struct syscall_trace_enter *rec)
 >  {
 >  	struct syscall_tp_t {
 > -		unsigned long long regs;
 > +		struct trace_entry ent;
 >  		unsigned long syscall_nr;
 >  		unsigned long args[SYSCALL_DEFINE_MAXARGS];
 >  	} param;
 >  	int i;
 
 > +	BUILD_BUG_ON(sizeof(param.ent) < sizeof(void *));
 > +
 > +	/* __bpf_prog_run() requires *regs as the first parameter */
 >  	*(struct pt_regs **)&param = regs;
 >  	param.syscall_nr = rec->nr;
 >  	for (i = 0; i < sys_data->nb_args; i++)
 > @@ -657,11 +660,14 @@ static int perf_call_bpf_exit(struct trace_event_call *call, struct pt_regs *reg
 >  			      struct syscall_trace_exit *rec)
 >  {
 >  	struct syscall_tp_t {
 > -		unsigned long long regs;
 > +		struct trace_entry ent;
 >  		unsigned long syscall_nr;
 >  		unsigned long ret;
 >  	} param;
 
 > +	BUILD_BUG_ON(sizeof(param.ent) < sizeof(void *));
 > +
 > +	/* __bpf_prog_run() requires *regs as the first parameter */
 >  	*(struct pt_regs **)&param = regs;
 >  	param.syscall_nr = rec->nr;
 >  	param.ret = rec->ret;
 > -- 

 > 2.41.0


-- 
WBR,
Yauheni Kaliuta


      reply	other threads:[~2023-07-27 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 15:05 [PATCH] tracing: perf_call_bpf: use struct trace_entry in struct syscall_tp_t Yauheni Kaliuta
2023-07-27 15:08 ` Yauheni Kaliuta [this message]

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=xunyzg3hpf2z.fsf@redhat.com \
    --to=ykaliuta@redhat.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.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 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.