From: "Dmitry V. Levin" <ldv@strace.io>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Oleg Nesterov <oleg@redhat.com>,
Eugene Syromyatnikov <evgsyr@gmail.com>,
Russell King <linux@armlinux.org.uk>, Kees Cook <kees@kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
Frederic Weisbecker <frederic@kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Jinjie Ruan <ruanjinjie@huawei.com>,
Arnd Bergmann <arnd@arndb.de>, Ard Biesheuvel <ardb@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 00/31] ARM: Switch to generic entry
Date: Fri, 14 Feb 2025 13:05:08 +0200 [thread overview]
Message-ID: <20250214110508.GA19194@strace.io> (raw)
In-Reply-To: <CACRpkdZJYFUhmPg3EWJeU42fzJMzWm7Sgn3XfELB2-PSCf6Ssw@mail.gmail.com>
On Fri, Feb 14, 2025 at 11:47:30AM +0100, Linus Walleij wrote:
> On Fri, Feb 14, 2025 at 2:03 AM Dmitry V. Levin <ldv@strace.io> wrote:
> > On Wed, Feb 12, 2025 at 12:22:54PM +0100, Linus Walleij wrote:
> > [...]
> > > - Tested some ptrace/strace obviously, such as issuing
> > > several instances of "ptrace find /" and let this scroll
> > > by in the terminal over some 10 minutes or so.
> >
> > Could you also run the strace test suite, please? Given that it used to
> > catch quite a few regressions in the past, it could be useful in this case
> > as well.
>
> Sure, where can I find this test suite?
It's a part of strace, you can find it e.g. at
https://github.com/strace/strace
To build and run it one can roughly do
./bootstrap && ./configure && make -j`nproc` && make -j`nproc check
--
ldv
next prev parent reply other threads:[~2025-02-14 11:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 11:22 [PATCH v4 00/31] ARM: Switch to generic entry Linus Walleij
2025-02-12 11:22 ` [PATCH v4 01/31] ARM: Prepare includes for " Linus Walleij
2025-02-12 11:22 ` [PATCH v4 02/31] ARM: ptrace: Split report_syscall() Linus Walleij
2025-02-12 11:22 ` [PATCH v4 03/31] ARM: entry: Skip ret_slow_syscall label Linus Walleij
2025-02-12 11:22 ` [PATCH v4 04/31] ARM: process: Rewrite ret_from_fork i C Linus Walleij
2025-02-12 11:22 ` [PATCH v4 05/31] ARM: process: Remove local restart Linus Walleij
2025-02-12 11:23 ` [PATCH v4 06/31] ARM: entry: Invoke syscalls using C Linus Walleij
2025-02-12 11:23 ` [PATCH v4 07/31] ARM: entry: Rewrite two asm calls in C Linus Walleij
2025-02-12 11:23 ` [PATCH v4 08/31] ARM: entry: Move trace entry to C function Linus Walleij
2025-02-12 11:23 ` [PATCH v4 09/31] ARM: entry: save the syscall sp in thread_info Linus Walleij
2025-02-12 11:23 ` [PATCH v4 10/31] ARM: entry: move all tracing invocation to C Linus Walleij
2025-02-12 11:23 ` [PATCH v4 11/31] ARM: entry: Merge the common and trace entry code Linus Walleij
2025-02-12 11:23 ` [PATCH v4 12/31] ARM: entry: Rename syscall invocation Linus Walleij
2025-02-12 11:23 ` [PATCH v4 13/31] ARM: entry: Create user_mode_enter/exit Linus Walleij
2025-02-12 11:23 ` [PATCH v4 14/31] ARM: entry: Drop trace argument from usr_entry macro Linus Walleij
2025-02-12 11:23 ` [PATCH v4 15/31] ARM: entry: Separate call path for syscall SWI entry Linus Walleij
2025-02-12 11:23 ` [PATCH v4 16/31] ARM: entry: Drop argument to asm_irqentry macros Linus Walleij
2025-02-12 11:23 ` [PATCH v4 17/31] ARM: entry: Implement syscall_exit_to_user_mode() Linus Walleij
2025-02-12 11:23 ` [PATCH v4 18/31] ARM: entry: Drop the superfast ret_fast_syscall Linus Walleij
2025-02-12 11:23 ` [PATCH v4 19/31] ARM: entry: Remove fast and offset register restore Linus Walleij
2025-02-12 11:23 ` [PATCH v4 20/31] ARM: entry: Untangle ret_fast_syscall/to_user Linus Walleij
2025-02-12 11:23 ` [PATCH v4 21/31] ARM: entry: Do not double-call exit functions Linus Walleij
2025-02-12 11:23 ` [PATCH v4 22/31] ARM: entry: Move work processing to C Linus Walleij
2025-02-12 11:23 ` [PATCH v4 23/31] ARM: entry: Stop exiting syscalls like IRQs Linus Walleij
2025-02-12 11:23 ` [PATCH v4 24/31] ARM: entry: Complete syscall and IRQ transition to C Linus Walleij
2025-02-12 11:23 ` [PATCH v4 25/31] ARM: entry: Create irqentry calls from kernel mode Linus Walleij
2025-02-12 11:23 ` [PATCH v4 26/31] ARM: entry: Move in-kernel hardirq tracing to C Linus Walleij
2025-02-12 11:23 ` [PATCH v4 27/31] ARM: irq: Add irqstack helper Linus Walleij
2025-02-12 11:23 ` [PATCH v4 28/31] ARM: entry: Convert to generic entry Linus Walleij
2025-02-12 11:23 ` [PATCH v4 29/31] ARM: entry: Handle dabt, pabt, and und as interrupts Linus Walleij
2025-02-12 11:23 ` [PATCH v4 30/31] ARM: entry: Block IRQs in early IRQ context Linus Walleij
2025-02-12 11:23 ` [PATCH v4 31/31] ARM: entry: Straighten syscall returns Linus Walleij
2025-02-15 4:10 ` kernel test robot
2025-02-14 1:03 ` [PATCH v4 00/31] ARM: Switch to generic entry Dmitry V. Levin
2025-02-14 10:47 ` Linus Walleij
2025-02-14 11:05 ` Dmitry V. Levin [this message]
2025-02-20 14:04 ` Linus Walleij
2025-02-20 14:30 ` Dmitry V. Levin
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=20250214110508.GA19194@strace.io \
--to=ldv@strace.io \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=dvyukov@google.com \
--cc=evgsyr@gmail.com \
--cc=frederic@kernel.org \
--cc=kees@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=paulmck@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wad@chromium.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.