From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756880Ab1GAOiU (ORCPT ); Fri, 1 Jul 2011 10:38:20 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:33730 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756689Ab1GAOiR (ORCPT ); Fri, 1 Jul 2011 10:38:17 -0400 Date: Fri, 1 Jul 2011 16:37:35 +0200 From: Ingo Molnar To: Christoph Hellwig Cc: Petr Tesarik , Andrew Morton , Fenghua Yu , "H. Peter Anvin" , Ingo Molnar , Paul Mundt , Russell King , Thomas Gleixner , Tony Luck , x86@kernel.org, linux-arm-kernel@lists.infradead.org, linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org, Arjan van de Ven , Dave Jones , Linus Torvalds Subject: Re: [PATCH 00/10] Enhance /dev/mem to allow read/write of arbitrary physical addresses Message-ID: <20110701143735.GA21367@elte.hu> References: <201106171038.25988.ptesarik@suse.cz> <20110617093032.GA19235@elte.hu> <201106291106.00070.ptesarik@suse.cz> <20110701125802.GE12605@elte.hu> <20110701134705.GA6175@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110701134705.GA6175@infradead.org> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.3.1 -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Christoph Hellwig wrote: > On Fri, Jul 01, 2011 at 02:58:02PM +0200, Ingo Molnar wrote: > > So what was not mentioned in your series, what is *your* motivation > > and your usecase? Enabling closed-source userspace drivers? Enabling > > the crash utility? > > He stated it pretty clearly in the thread, it's the crash utility. True. I only re-read the first patch and forgot about the resulting discussion. Sorry Petr! > > If the former then shame on you, if the latter then how do you > > explain that distros appear to disable the RAM aspect of > > /dev/mem: > > > > $ grep DEVMEM $(rpm -ql kernel-2.6.38-0.rc7.git2.3.fc16.x86_64 | grep config-2.6 ) > > CONFIG_STRICT_DEVMEM=y > > > > So the crash utility use-case does not work on unpatched, default > > kernels, right? > > Not if you have highmem. That's why Redhat or Fedora to quote your > example patch in the /dev/crash driver, which totally defeats the > CONFIG_STRICT_DEVMEM setting. But apparently it's good enough that no > one either noticed or at least doesn't care. After initial modules have loaded i essentially disable crash.ko via /proc/sys/kernel/modules_disabled so rootkits have to work a bit harder than that. But yeah, crash.ko is a rootkit-and-other-badness-enabler as it stands today. Thanks, Ingo