Date: Sat, 11 Sep 2010 01:01:59 -0700 From: perryh@pluto.rain.com To: jhb@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Re: MSIX failure Message-ID: <4c8b3777.A5l69BLBx5dsBnNl%perryh@pluto.rain.com> In-Reply-To: <201009100757.49777.jhb@freebsd.org> References: <AANLkTikvd09fw3fUhxsXDhMoWE-kvMoPjXPSTfzYY73T@mail.gmail.com> <20100909150012.GA27370@lordcow.org> <4c89d653.UyUz1Sv9zPckJnig%perryh@pluto.rain.com> <201009100757.49777.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin <jhb@freebsd.org> 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 <bsd@lordcow.org> (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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4c8b3777.A5l69BLBx5dsBnNl%perryh>