From: Kees Cook <keescook@chromium.org>
To: Russell King <linux@armlinux.org.uk>
Cc: Kees Cook <keescook@chromium.org>,
Arnd Bergmann <arnd@kernel.org>,
Lecopzer Chen <lecopzer.chen@mediatek.com>,
Oleg Nesterov <oleg@redhat.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Linus Walleij <linus.walleij@linaro.org>,
Wolfram Sang <wsa@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Dan Williams <dan.j.williams@intel.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-hardening@vger.kernel.org
Subject: [PATCH v2 0/2] ARM: ptrace: Restore syscall skipping and restart while tracing
Date: Thu, 10 Aug 2023 12:54:17 -0700 [thread overview]
Message-ID: <20230810195141.never.338-kees@kernel.org> (raw)
Hi,
Fix tracing on arm since commit 4e57a4ddf6b0 ("ARM: 9107/1: syscall:
always store thread_info->abi_syscall"). This was seen with the broken
seccomp tests "syscall_errno", "syscall_faked", and "syscall_restart".
Thanks!
-Kees
v2:
- split fixes
- move scno store into the actual restart path
v1: https://lore.kernel.org/lkml/20230804071045.never.134-kees@kernel.org
Kees Cook (2):
ARM: ptrace: Restore syscall restart tracing
ARM: ptrace: Restore syscall skipping for tracers
arch/arm/include/asm/syscall.h | 3 +++
arch/arm/kernel/entry-common.S | 1 +
arch/arm/kernel/ptrace.c | 5 +++--
3 files changed, 7 insertions(+), 2 deletions(-)
--
2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Russell King <linux@armlinux.org.uk>
Cc: Kees Cook <keescook@chromium.org>,
Arnd Bergmann <arnd@kernel.org>,
Lecopzer Chen <lecopzer.chen@mediatek.com>,
Oleg Nesterov <oleg@redhat.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Linus Walleij <linus.walleij@linaro.org>,
Wolfram Sang <wsa@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Dan Williams <dan.j.williams@intel.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-hardening@vger.kernel.org
Subject: [PATCH v2 0/2] ARM: ptrace: Restore syscall skipping and restart while tracing
Date: Thu, 10 Aug 2023 12:54:17 -0700 [thread overview]
Message-ID: <20230810195141.never.338-kees@kernel.org> (raw)
Hi,
Fix tracing on arm since commit 4e57a4ddf6b0 ("ARM: 9107/1: syscall:
always store thread_info->abi_syscall"). This was seen with the broken
seccomp tests "syscall_errno", "syscall_faked", and "syscall_restart".
Thanks!
-Kees
v2:
- split fixes
- move scno store into the actual restart path
v1: https://lore.kernel.org/lkml/20230804071045.never.134-kees@kernel.org
Kees Cook (2):
ARM: ptrace: Restore syscall restart tracing
ARM: ptrace: Restore syscall skipping for tracers
arch/arm/include/asm/syscall.h | 3 +++
arch/arm/kernel/entry-common.S | 1 +
arch/arm/kernel/ptrace.c | 5 +++--
3 files changed, 7 insertions(+), 2 deletions(-)
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-08-10 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 19:54 Kees Cook [this message]
2023-08-10 19:54 ` [PATCH v2 0/2] ARM: ptrace: Restore syscall skipping and restart while tracing Kees Cook
2023-08-10 19:54 ` [PATCH v2 1/2] ARM: ptrace: Restore syscall restart tracing Kees Cook
2023-08-10 19:54 ` Kees Cook
2023-08-10 20:17 ` Arnd Bergmann
2023-08-10 20:17 ` Arnd Bergmann
2023-08-10 19:54 ` [PATCH v2 2/2] ARM: ptrace: Restore syscall skipping for tracers Kees Cook
2023-08-10 19:54 ` Kees Cook
2023-08-10 20:11 ` Arnd Bergmann
2023-08-10 20:11 ` Arnd Bergmann
2023-08-11 5:55 ` [PATCH v2 0/2] ARM: ptrace: Restore syscall skipping and restart while tracing Kees Cook
2023-08-11 5:55 ` Kees Cook
2023-08-16 20:59 ` Kees Cook
2023-08-16 20:59 ` Kees Cook
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=20230810195141.never.338-kees@kernel.org \
--to=keescook@chromium.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=lecopzer.chen@mediatek.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=oleg@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=wsa@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.