From owner-freebsd-hackers  Sat Dec  2 13:39:49 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 42F8937B400; Sat,  2 Dec 2000 13:39:41 -0800 (PST)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA05165;
	Sat, 2 Dec 2000 16:39:39 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eB2LddK11533;
	Sat, 2 Dec 2000 16:39:39 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sat,  2 Dec 2000 16:39:39 -0500 (EST)
To: "Kenneth D. Merry" <ken@kdm.org>
Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG
Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission?
In-Reply-To: <20001201174408.A17122@panzer.kdm.org>
References: <200012012056.eB1KuDI32343@orthanc.ab.ca>
	<20001201174408.A17122@panzer.kdm.org>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14889.27531.660040.955219@grasshopper.cs.duke.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Kenneth D. Merry writes:
 > As for PCIOCREAD, it only allows reading of PCI registers, so the question
 > there is whether there are any potential security implications to allowing
 > non-root users to read PCI registers.  If reading configuration registers
 > caused performance degredation, for instance.

I think that you might be able to crash an alpha with an unaligned
access trap by reading an int or short an from an unaligned offset in
config space.  At least this used to be true..  I'd vote for leaving
the access permissions as is. 

Drew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message