Date: Mon, 16 Jun 2003 15:00:22 -0700 From: John-Mark Gurney <gurney_j@efn.org> To: Scott Long <scottl@freebsd.org> Cc: Robert Watson <rwatson@freebsd.org> Subject: Re: make /dev/pci really readable Message-ID: <20030616220022.GW73854@funkthat.com> In-Reply-To: <3EEE3BF2.3020809@freebsd.org> References: <20030616074122.GF73854@funkthat.com> <Pine.NEB.3.96L.1030616135002.8726B-100000@fledge.watson.org> <20030616194935.GR73854@funkthat.com> <3EEE2B31.4020406@freebsd.org> <20030616213312.GV73854@funkthat.com> <3EEE3BF2.3020809@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long wrote this message on Mon, Jun 16, 2003 at 15:51 -0600:
> John-Mark Gurney wrote:
> >hmmm. are you sure about this? wouldn't it mean that by simply probing
> >for a device you could end up locking up the system?
> >
>
> The first 64 bytes in the space is likely safe, from bytes 65-255 it is
> entirely vendor specific.
ok, agreed.. Dare I ask that we let normal users read the first 64
bytes? and require write permissions to read about 64? :) just kidding..
> I'll not argue your development practices. However, I don't see it as
> unreasonable to ask that driver writers who are going to need root
> access to do their work anyways (modifying files, compiling kernels
> and/or loading modules) also use root to access the pci registers from
> userland.
everything up to the loading modules I like to do as normal user..
> I seem to remember Linx having a similar feature a few years ago and
> naive sysadmins getting into serious trouble by pointing their tape
> backups at the /proc/pci directory.
:) well, lucky for use /dev/pci doesn't have a write interface.. :)
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030616220022.GW73854>