From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] arm64: Unimplemented syscall kernel message
Date: Mon, 19 Feb 2018 15:39:35 +0000 [thread overview]
Message-ID: <20180219153934.GA1740@arm.com> (raw)
In-Reply-To: <20180201221338.9952-1-michael.weiser@gmx.de>
Hi Michael,
On Thu, Feb 01, 2018 at 11:13:35PM +0100, Michael Weiser wrote:
> I've dropped the message from the compat change, which makes it much
> more straight-forward. We are still dropping the offending log message
> from do_ni_syscall(). The second change now just mirrors the part of arm
> behaviour in compat_arm_syscall() that raises SIGILL for (most)
> unimplemented syscalls. Finally show_unhandled_signals is disabled by
> default.
>
> All are compile-tested as well as manually prodded with some randomly
> chosen syscall numbers from aarch64 and arm-eabi binaries while running
> under qemu-system-aarch64. New show_unhandled_signals defaults and
> enabling via /proc/sys have been tested with a minimal segfaulting test
> program.
Thanks, I'll pick these up for 4.17.
Will
prev parent reply other threads:[~2018-02-19 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 17:44 arm64: Unimplemented syscall kernel message Michael Weiser
2018-01-22 13:18 ` Will Deacon
2018-01-22 21:20 ` [PATCH 0/2] " Michael Weiser
2018-01-22 21:20 ` [PATCH 1/2] arm64: Remove unimplemented syscall log message Michael Weiser
2018-01-29 15:38 ` Will Deacon
2018-01-22 21:20 ` [PATCH 2/2] arm64: Mirror arm for unimplemented compat syscalls Michael Weiser
2018-01-29 15:37 ` Will Deacon
2018-02-01 22:13 ` [PATCH v2 0/2] arm64: Unimplemented syscall kernel message Michael Weiser
2018-02-01 22:13 ` [PATCH v2 1/3] arm64: Remove unimplemented syscall log message Michael Weiser
2018-02-01 22:13 ` [PATCH v2 2/3] arm64: Mirror arm for unimplemented compat syscalls Michael Weiser
2018-02-01 22:13 ` [PATCH v2 3/3] arm64: Disable unhandled signal log messages by default Michael Weiser
2018-02-19 15:39 ` Will Deacon [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=20180219153934.GA1740@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.