From: Arjan van de Ven <arjan@infradead.org>
To: Bernhard Walle <bwalle@suse.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, Bernhard Walle <bwalle@suse.de>
Subject: Re: [PATCH 2/2] Add dev.mem.restricted sysctl
Date: Sat, 15 Nov 2008 19:49:14 -0800 [thread overview]
Message-ID: <20081115194914.6791b96c@infradead.org> (raw)
In-Reply-To: <1226793823-32360-3-git-send-email-bwalle@suse.de>
On Sun, 16 Nov 2008 01:03:43 +0100
Bernhard Walle <bwalle@suse.de> wrote:
> When CONFIG_STRICT_DEVMEM is set, live debugging is not possible with
> the crash utility (see http://people.redhat.com/~anderson). For
> distributors who ship a generic kernel it's difficult: Disabling
> CONFIG_STRICT_DEVMEM is possible, but in general the protection
> provided by CONFIG_STRICT_DEVMEM is useful. However, live debugging
> should be still neceessary.
>
> This patch now adds a dev.mem.restricted sysctl that defaults to 0
> (off). When set to 1 (on), /dev/mem access is unrestricted and crash
> can be used.
>
sounds like a really bad idea to me.
If you want to use /dev/mem like this, don't enable the config option
to restrict it. Really.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-11-16 3:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 0:03 [RFC] " Bernhard Walle
2008-11-16 0:03 ` [PATCH 1/2] Unify devmem_is_allowed across architectures Bernhard Walle
2008-11-16 0:03 ` [PATCH 2/2] Add dev.mem.restricted sysctl Bernhard Walle
2008-11-16 0:07 ` Alan Cox
2008-11-16 0:09 ` Bernhard Walle
2008-11-16 0:12 ` Alan Cox
2008-11-16 0:11 ` Bernhard Walle
2008-11-16 0:33 ` Alexey Dobriyan
2008-11-16 9:28 ` Bernhard Walle
2008-11-16 10:13 ` Alexey Dobriyan
2008-11-16 3:49 ` Arjan van de Ven [this message]
2008-11-16 9:30 ` Bernhard Walle
2008-11-16 9:36 ` Arjan van de Ven
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=20081115194914.6791b96c@infradead.org \
--to=arjan@infradead.org \
--cc=bwalle@suse.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®