From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: Turn CONFIG_STRICT_DEVMEM in sysctl dev.mem.restricted Date: Sun, 16 Nov 2008 12:32:46 -0800 Message-ID: <4920836E.1080803@kernel.org> References: <1226846868-9595-1-git-send-email-bwalle@suse.de> <20081116073948.02aea58c@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from terminus.zytor.com ([198.137.202.10]:46340 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752287AbYKPUgX (ORCPT ); Sun, 16 Nov 2008 15:36:23 -0500 In-Reply-To: <20081116073948.02aea58c@infradead.org> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Arjan van de Ven Cc: Bernhard Walle , x86@kernel.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, crash-utility@redhat.com Arjan van de Ven wrote: > > I assume /dev/crash is read only > > but your series still makes absolutely no sense to me... > really. Nak. > > You either want this at compile time or you don't want it at all. > You could certainly envision this as a boottime option, or even a *one-way* settable runtime option (kind of like the BSD securelevel idea.) The question is to which extent even that makes any sense. -hpa