linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	bpf@vger.kernel.org, Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH] bpf/selftests: Fix __NR_uretprobe in uprobe_syscall test
Date: Tue, 18 Jun 2024 21:33:02 +0200	[thread overview]
Message-ID: <ZnHg7tuVdfOc_5Dq@krava> (raw)
In-Reply-To: <Zm9CNlPVfmV_Pc-S@krava>

On Sun, Jun 16, 2024 at 09:51:18PM +0200, Jiri Olsa wrote:
> On Sun, Jun 16, 2024 at 01:19:11AM +0900, Masami Hiramatsu wrote:
> > On Sun, 16 Jun 2024 00:19:20 +0900
> > Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> > 
> > > On Fri, 14 Jun 2024 12:15:09 +0200
> > > Jiri Olsa <jolsa@kernel.org> wrote:
> > > 
> > > > Fixing the __NR_uretprobe number in uprobe_syscall test,
> > > > because it changed due to merge conflict.
> > > > 
> > > 
> > > Ah, it is not enough, since Stephen's change is just a temporary fix on
> > > next tree. OK, Let me update it.
> > 
> > Hm, I thought I need to change all NR_uretprobe, but it makes NR_syscalls
> > list sparse. This may need to be solved on linus tree in merge window,
> > or I should merge (or rebase on) vfs-brauner tree before sending
> > probes/for-next.
> > 
> > Steve, do you have any idea? we talked about conflict on next tree[0].
> > 
> > [0] https://lore.kernel.org/all/20240613114243.2a50059b@canb.auug.org.au/
> 
> hi,
> I have one more fix to send [1] for this, please let me know which tree
> I should based that on

hi,
any news on this?

thanks,
jirka

> 
> thanks,
> jirka
> 
> 
> [1] https://lore.kernel.org/bpf/ZmyZgzqsowkGyqmH@krava/
> 
> > 
> > Thanks,
> > 
> > > 
> > > Thanks,
> > > 
> > > > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> > > > ---
> > > >  tools/testing/selftests/bpf/prog_tests/uprobe_syscall.c | 2 +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > 
> > > > diff --git a/tools/testing/selftests/bpf/prog_tests/uprobe_syscall.c b/tools/testing/selftests/bpf/prog_tests/uprobe_syscall.c
> > > > index c8517c8f5313..bd8c75b620c2 100644
> > > > --- a/tools/testing/selftests/bpf/prog_tests/uprobe_syscall.c
> > > > +++ b/tools/testing/selftests/bpf/prog_tests/uprobe_syscall.c
> > > > @@ -216,7 +216,7 @@ static void test_uretprobe_regs_change(void)
> > > >  }
> > > >  
> > > >  #ifndef __NR_uretprobe
> > > > -#define __NR_uretprobe 463
> > > > +#define __NR_uretprobe 467
> > > >  #endif
> > > >  
> > > >  __naked unsigned long uretprobe_syscall_call_1(void)
> > > > -- 
> > > > 2.45.1
> > > > 
> > > 
> > > 
> > > -- 
> > > Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > 
> > 
> > -- 
> > Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2024-06-18 19:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14 10:15 [PATCH] bpf/selftests: Fix __NR_uretprobe in uprobe_syscall test Jiri Olsa
2024-06-15 15:19 ` Masami Hiramatsu
2024-06-15 16:19   ` Masami Hiramatsu
2024-06-16 19:51     ` Jiri Olsa
2024-06-18 19:33       ` Jiri Olsa [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=ZnHg7tuVdfOc_5Dq@krava \
    --to=olsajiri@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=nathan@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).