linux-kernel - Re: [GIT PULL] probes: Updates for v6.11

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20240719102150.197c7fc7459459a8c439d972@kernel.org>
Date: Fri, 19 Jul 2024 10:21:50 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
 "Masami Hiramatsu (Google)" <mhiramat@...nel.org>, Andrii Nakryiko
 <andrii@...nel.org>, Jeff Johnson <quic_jjohnson@...cinc.com>, Jiri Olsa
 <jolsa@...nel.org>, Steven Rostedt <rostedt@...dmis.org>,
 linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] probes: Updates for v6.11

On Fri, 19 Jul 2024 10:28:24 +1000
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi Linus,
> 
> On Tue, 16 Jul 2024 23:44:45 +0900 Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:
> >
> > Probes updates for v6.11:
> > 
> > Uprobes:
> > - x86/shstk: Make return uprobe work with shadow stack.
> > - Add uretprobe syscall which speeds up the uretprobe 10-30% faster. This
> >   syscall is automatically used from user-space trampolines which are
> >   generated by the uretprobe. If this syscall is used by normal
> >   user program, it will cause SIGILL. Note that this is currently only
> >   implemented on x86_64.
> >   (This also has 2 fixes for adjusting the syscall number to avoid conflict
> >    with new *attrat syscalls.)
> 
> But another fix that I have been carrying was missed:
> 
> https://lore.kernel.org/lkml/20240717132155.6ca2ce47@canb.auug.org.au/
> 
> Just the added change to scripts/syscall.tbl (and obviously needs
> adjusting because the *xattrat* syscalss have not been merged yet).

Ah, I thought that was for helping Linus when he merge the commits.
And actually, this number is used in other part (e.g. testing), I added it.
When xattarat syscalls are merged (until -rc1?), this difference is solved,
isn't it?

Thank you,

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