[Observed on 4.2-STABLE, but I've redirected replies to the hackers list.] 'pciconf -l' is documented to work for non-priv users, however the first thing the underlying ioctl code (pci_ioctl) does is bail with EPERM if the caller does not have /dev/pci open for write. Is there any reason why the FWRITE test cannot/should not be moved down into the 'case PCIOCWRITE' part of the switch? This would make both PCIOCGETCONF and PCIOCREAD work for readonly access to /dev/pci (which seems to me to be saner behaviour). --lyndon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: PCIOCGETCONF/PCIOCREAD requires write permission? Lyndon Nerenberg
- Re: PCIOCGETCONF/PCIOCREAD requires write permission... Kenneth D. Merry
- Re: PCIOCGETCONF/PCIOCREAD requires write permis... Andrew Gallatin
- Re: PCIOCGETCONF/PCIOCREAD requires write pe... Matthew Jacob
- Re: PCIOCGETCONF/PCIOCREAD requires writ... Chad R. Larson
- Re: PCIOCGETCONF/PCIOCREAD requires... Warner Losh
- Re: PCIOCGETCONF/PCIOCREAD requires... Mike Silbersack
- Re: Re: PCIOCGETCONF/PCIOCREAD ... Stefan Esser
- Re: PCIOCGETCONF/PCIOCREAD requires... David O'Brien
- Re: PCIOCGETCONF/PCIOCREAD requ... Daniel C. Sobral
- Re: PCIOCGETCONF/PCIOCREAD ... Wes Peters