From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: Turn CONFIG_STRICT_DEVMEM in sysctl dev.mem.restricted Date: Sun, 16 Nov 2008 07:39:48 -0800 Message-ID: <20081116073948.02aea58c@infradead.org> References: <1226846868-9595-1-git-send-email-bwalle@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from casper.infradead.org ([85.118.1.10]:38290 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752684AbYKPPjF (ORCPT ); Sun, 16 Nov 2008 10:39:05 -0500 In-Reply-To: <1226846868-9595-1-git-send-email-bwalle@suse.de> Sender: linux-arch-owner@vger.kernel.org List-ID: Cc: x86@kernel.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, crash-utility@redhat.com, Bernhard Walle On Sun, 16 Nov 2008 15:47:45 +0100 Bernhard Walle wrote: > While the original submission of CONFIG_STRICT_DEVMEM mentions that > the option has been in RHEL and Fedora for 4 years without problems, > that's only a half of the story. The truth is that at least RHEL > has /dev/crash exactly to circumvent that /dev/mem restriction. Don't > tell me that this is better than having that sysctl entry. ;-) 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. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from casper.infradead.org ([85.118.1.10]:38290 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752684AbYKPPjF (ORCPT ); Sun, 16 Nov 2008 10:39:05 -0500 Date: Sun, 16 Nov 2008 07:39:48 -0800 From: Arjan van de Ven Subject: Re: Turn CONFIG_STRICT_DEVMEM in sysctl dev.mem.restricted Message-ID: <20081116073948.02aea58c@infradead.org> In-Reply-To: <1226846868-9595-1-git-send-email-bwalle@suse.de> References: <1226846868-9595-1-git-send-email-bwalle@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org List-ID: To: Bernhard Walle Cc: x86@kernel.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, crash-utility@redhat.com Message-ID: <20081116153948.6oGtfjx6QnW1WIKgH3PkK9_FTdjn7Mnc9uj-ALzo_aM@z> On Sun, 16 Nov 2008 15:47:45 +0100 Bernhard Walle wrote: > While the original submission of CONFIG_STRICT_DEVMEM mentions that > the option has been in RHEL and Fedora for 4 years without problems, > that's only a half of the story. The truth is that at least RHEL > has /dev/crash exactly to circumvent that /dev/mem restriction. Don't > tell me that this is better than having that sysctl entry. ;-) 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. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org