From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: defconfig: disable CONFIG_DEVMEM
Date: Fri, 13 Jan 2017 11:48:01 +0000 [thread overview]
Message-ID: <20170113114801.GD3253@arm.com> (raw)
In-Reply-To: <20170113113734.16524-1-leif.lindholm@linaro.org>
On Fri, Jan 13, 2017 at 11:37:34AM +0000, Leif Lindholm wrote:
> /dev/mem is the opposite of what an operating system is for.
> Additionally, on arm* it opens up for denial-of-service attacks from
> userspace. So leave it disabled by default, requiring people who need
> it to enable it explicitly.
I really like the idea, but are we sure that nothing common breaks without
this? For example, does Debian still boot nicely with this patch applied?
Just trying to get a feel for how much userspace this has seen (particularly
on ACPI-based systems, which I seem to remember like poking about in here).
Will
next prev parent reply other threads:[~2017-01-13 11:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 11:37 [PATCH] arm64: defconfig: disable CONFIG_DEVMEM Leif Lindholm
2017-01-13 11:38 ` Ard Biesheuvel
2017-01-13 11:40 ` Mark Rutland
2017-01-13 11:48 ` Will Deacon [this message]
2017-01-15 12:42 ` Leif Lindholm
2017-01-16 13:40 ` Leif Lindholm
2017-01-18 17:58 ` Leif Lindholm
2017-01-19 9:49 ` Will Deacon
2017-01-20 14:42 ` Leif Lindholm
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=20170113114801.GD3253@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 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).