[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 1 Jul 2022 16:41:28 +0100
From: Will Deacon <will@...nel.org>
To: linux-trace-devel@...r.kernel.org,
Francis Laniel <flaniel@...ux.microsoft.com>
Cc: catalin.marinas@....com, kernel-team@...roid.com,
Will Deacon <will@...nel.org>,
Palmer Dabbelt <palmer@...belt.com>,
Peter Collingbourne <pcc@...gle.com>,
Mark Brown <broonie@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
linux-arm-kernel@...ts.infradead.org,
Mark Rutland <mark.rutland@....com>,
Kees Cook <keescook@...omium.org>,
Daniel Kiss <daniel.kiss@....com>,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
James Morse <james.morse@....com>,
Albert Ou <aou@...s.berkeley.edu>
Subject: Re: [PATCH v2 0/1] Remove forget_syscall() from start_thread_common()
On Wed, 8 Jun 2022 17:24:45 +0100, Francis Laniel wrote:
> First, I hope you are fine and the same for your relatives.
>
> With this contribution, I enabled using syscalls:sys_exit_execve and
> syscalls:sys_exit_execveat as tracepoints on arm64.
> Indeed, before this contribution, the above tracepoint would not print their
> information as syscall number was set to -1 by calling forget_syscall().
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64: Do not forget syscall when starting a new thread.
https://git.kernel.org/arm64/c/de6921856f99
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists