From owner-freebsd-bugs Mon Dec 10 12:10:10 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B110637B41B for ; Mon, 10 Dec 2001 12:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id fBAKA2R25346; Mon, 10 Dec 2001 12:10:02 -0800 (PST) (envelope-from gnats) Date: Mon, 10 Dec 2001 12:10:02 -0800 (PST) Message-Id: <200112102010.fBAKA2R25346@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Brooks Davis Subject: Re: kern/32677: pciconf -l opens /dev/pci for O_RDWR Reply-To: Brooks Davis Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/32677; it has been noted by GNATS. From: Brooks Davis To: seth@psychotic.aberrant.org Cc: FreeBSD-gnats-submit@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: kern/32677: pciconf -l opens /dev/pci for O_RDWR Date: Mon, 10 Dec 2001 12:00:05 -0800 On Mon, Dec 10, 2001 at 01:06:15PM -0500, seth@psychotic.aberrant.org wrote: > Check arguments to pciconf. If -l, open O_RDONLY. This doesn't actually work. The current ioctl access controls require that you have the device opened for write in all cases. This is a rather odd check, but it's the case. My recollection of the last conversation about this on the lists is that on some configurations the ability to read pci state is the ability to crash the system so it is restricted. It seems PCIOCGETCONF and PCIOCREAD should probalby be allowed if the user can read the device and the device nodes should be fixed to be unreadable to non-root users, but there may be some reason for the current configuration that I don't know about. I've CC'd Mike Smith for his opinion on this. -- Brooks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message