linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Dave.Martin@arm.com (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Trap WFI executed in userspace
Date: Tue, 7 Aug 2018 11:05:02 +0100	[thread overview]
Message-ID: <20180807100437.GA9097@e103592.cambridge.arm.com> (raw)
In-Reply-To: <20180807093326.5090-1-marc.zyngier@arm.com>

On Tue, Aug 07, 2018 at 10:33:26AM +0100, Marc Zyngier wrote:
> It recently came to light that userspace can execute WFI, and that
> the arm64 kernel doesn trap this event. This sounds rather benign,
> but the kernel should decide when it wants to wait for an interrupt,
> and not userspace.
> 
> Let's trap WFI and treat it as a way to yield the CPU to another
> process.

This doesn't amount to a justification.

If the power controller is unexpectedly left in a bad state so that
WFI will do something nasty to a cpu that may enter userspace, then we
probably have bigger problems.

So, maybe it really is pretty harmless to let userspace execute this.

I can't think of a legitimate reason for userspace to execute WFI
however.  Userspace doesn't have interrupts under Linux, so it makes
no sense to wait for one.

Have we seen anybody using WFI in userspace?  It may be cleaner to
map this to SIGILL rather than be permissive and regret it later.

[...]

Cheers
---Dave

  reply	other threads:[~2018-08-07 10:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07  9:33 [PATCH] arm64: Trap WFI executed in userspace Marc Zyngier
2018-08-07 10:05 ` Dave Martin [this message]
2018-08-07 10:24   ` Marc Zyngier
2018-08-07 10:30     ` Dave Martin
2018-08-07 12:12       ` Robin Murphy
2018-08-07 13:02         ` Dave Martin
2018-08-08 12:34     ` Catalin Marinas
2018-08-09 12:34       ` Dave Martin
2018-08-09 12:38         ` Will Deacon
2018-08-09 12:47           ` Dave Martin
2018-08-09 13:25             ` Marc Zyngier
2018-09-20 22:04 ` Pavel Machek
2018-09-20 22:33   ` Marc Zyngier

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=20180807100437.GA9097@e103592.cambridge.arm.com \
    --to=dave.martin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).