From owner-freebsd-stable@FreeBSD.ORG Sat Sep 11 08:11:02 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00C1D106566C; Sat, 11 Sep 2010 08:11:02 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id A2AA78FC13; Sat, 11 Sep 2010 08:11:01 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id o8B8B09X051008 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 11 Sep 2010 01:11:00 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id o8B8B070051007; Sat, 11 Sep 2010 01:11:00 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA16208; Sat, 11 Sep 10 01:05:37 PDT Date: Sat, 11 Sep 2010 01:01:59 -0700 From: perryh@pluto.rain.com To: jhb@freebsd.org Message-Id: <4c8b3777.A5l69BLBx5dsBnNl%perryh@pluto.rain.com> References: <20100909150012.GA27370@lordcow.org> <4c89d653.UyUz1Sv9zPckJnig%perryh@pluto.rain.com> <201009100757.49777.jhb@freebsd.org> In-Reply-To: <201009100757.49777.jhb@freebsd.org> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: MSIX failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 08:11:02 -0000 John Baldwin wrote: > On Friday, September 10, 2010 2:55:15 am perryh@pluto.rain.com wrote: > > ... > > It is arguably a bug to open O_RDWR when only examining things. > > You have to have RDWR permission to issue the ioctl to read config > registers which pciconf does when examining capabilities. So much for avoiding a reboot for (or whatever the correct address is -- that one bounced), but now it is beginning to look as if there may be a POLA violation at a lower level. Unless there are devices out there whose state can be changed by merely _reading_ (not writing) their configuration registers, I would not expect to need RDWR permission just to read them.