From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64: Remove unimplemented syscall log message
Date: Mon, 29 Jan 2018 15:38:39 +0000 [thread overview]
Message-ID: <20180129153839.GB24444@arm.com> (raw)
In-Reply-To: <20180122212026.26262-2-michael.weiser@gmx.de>
On Mon, Jan 22, 2018 at 10:20:25PM +0100, Michael Weiser wrote:
> Stop printing a (ratelimited) kernel message for each instance of an
> unimplemented syscall being called. Userland making an unimplemented
> syscall is not necessarily misbehaviour and to be expected with a
> current userland running on an older kernel. Also, the current message
> looks scary to users but does not actually indicate a real problem nor
> help them narrow down the cause. Just rely on sys_ni_syscall() to return
> -ENOSYS.
>
> Signed-off-by: Michael Weiser <michael.weiser@gmx.de>
> ---
> arch/arm64/kernel/traps.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c
> index bbb0fde2780e..0ef28b7f6aa7 100644
> --- a/arch/arm64/kernel/traps.c
> +++ b/arch/arm64/kernel/traps.c
> @@ -526,14 +526,6 @@ asmlinkage long do_ni_syscall(struct pt_regs *regs)
> }
> #endif
>
> - if (show_unhandled_signals_ratelimited()) {
> - pr_info("%s[%d]: syscall %d\n", current->comm,
> - task_pid_nr(current), regs->syscallno);
> - dump_instr("", regs);
> - if (user_mode(regs))
> - __show_regs(regs);
> - }
> -
> return sys_ni_syscall();
> }
Acked-by: Will Deacon <will.deacon@arm.com>
I'm also strongly inclined to change the default value of
show_unhandled_signals to be zero. I find it odd that it defaults to 1
when it can be changed via proc anyway, although this is consistent with
other architectures.
Will
next prev parent reply other threads:[~2018-01-29 15:38 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 [this message]
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 ` [PATCH v2 0/2] arm64: Unimplemented syscall kernel message Will Deacon
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=20180129153839.GB24444@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.