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 [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- PCIOCGETCONF/PCIOCREAD requires write permission? Lyndon Nerenberg
- Re: PCIOCGETCONF/PCIOCREAD requires write permiss... Kenneth D. Merry
- Re: PCIOCGETCONF/PCIOCREAD requires write per... Andrew Gallatin
- Re: PCIOCGETCONF/PCIOCREAD requires write... Matthew Jacob
- Re: PCIOCGETCONF/PCIOCREAD requires w... Chad R. Larson
- Re: PCIOCGETCONF/PCIOCREAD requi... Warner Losh
- Re: PCIOCGETCONF/PCIOCREAD requi... Mike Silbersack
- Re: Re: PCIOCGETCONF/PCIOCRE... Stefan Esser
- Re: PCIOCGETCONF/PCIOCREAD requi... David O'Brien
- Re: PCIOCGETCONF/PCIOCREAD r... Daniel C. Sobral
- Re: PCIOCGETCONF/PCIOCRE... Wes Peters
- Re: PCIOCGETCONF/PCIOCRE... Dag-Erling Smorgrav
- Re: PCIOCGETCONF/PCIOCRE... Wes Peters