Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751789Ab1FTAxC (ORCPT ); Sun, 19 Jun 2011 20:53:02 -0400 Received: from palinux.external.hp.com ([192.25.206.14]:48454 "EHLO mail.parisc-linux.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751222Ab1FTAw7 (ORCPT ); Sun, 19 Jun 2011 20:52:59 -0400 Date: Sun, 19 Jun 2011 18:52:55 -0600 From: Matthew Wilcox To: Ryan Mallon Cc: Ingo Molnar , 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: <20110620005255.GF19693@parisc-linux.org> References: <201106171038.25988.ptesarik@suse.cz> <20110617093032.GA19235@elte.hu> <4DFE7FF9.9070406@gmail.com> <20110620004252.GE19693@parisc-linux.org> <4DFE9850.7030400@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DFE9850.7030400@gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1822 Lines: 37 On Mon, Jun 20, 2011 at 10:46:08AM +1000, Ryan Mallon wrote: > On 20/06/11 10:42, Matthew Wilcox wrote: >> On Mon, Jun 20, 2011 at 09:02:17AM +1000, Ryan Mallon wrote: >>> There are drivers where this makes sense. For example an FPGA device >>> with a proprietary register layout on the memory bus can be done this >>> way. The FPGA can simply be mapped in user-space via /dev/mem and >>> handled there. If the device requires no access other than memory bus >>> reads and writes then writing a custom char device driver just to get an >>> mmap function seems a bit overkill. >> Calling a 30 line device driver "overkill" might in itself be overkill? >> > I mean overkill in the sense of having to write the driver at all. Why > write a 30 line driver just to re-implement some functionality of > /dev/mem? Because it pushes the tradeoff in the right direction. Somebody wants to do something weird is a little inconvenienced vs protecting the vast majority of users from some security escalation problems. Besides, if you have a real bus with discoverable regions (like PCI BARs), the bus should have sysfs entries like /sys/bus/pci/devices/0000\:06\:06.0/resource0 that can be mmaped. Then there's no need for a device driver at all, *and* the privilege escalation isn't achievable. Of course, most embedded architectures have crap discoverability. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/