From: Greg KH <greg@kroah.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Matthias Andree <matthias.andree@gmx.de>,
linux-scsi@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>,
gregkh@kroah.com
Subject: Re: 53C8XX /sys/devices/pci*/*/config revisited
Date: Sun, 15 May 2005 10:57:30 -0700 [thread overview]
Message-ID: <20050515175730.GA3898@kroah.com> (raw)
In-Reply-To: <1116156415.6270.19.camel@laptopd505.fenrus.org>
On Sun, May 15, 2005 at 01:26:55PM +0200, Arjan van de Ven wrote:
>
> > if hal reads more than 64 bytes of config space (heck if it reads config
> > space at all) then it's terminally broken.
>
> this brings up a bug in the kernel though....
> the config file is user readable! That's just plain dangerous and imo it
> should be a root-only file as a result.
No, it's safe (or it should be), just like /proc/bus/pci is readable by
anyone for libpci.
thanks,
greg k-h
prev parent reply other threads:[~2005-05-15 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 11:02 53C8XX /sys/devices/pci*/*/config revisited Matthias Andree
2005-05-15 11:13 ` Arjan van de Ven
2005-05-15 11:26 ` Arjan van de Ven
2005-05-15 12:56 ` Matthias Andree
2005-05-15 14:48 ` Matthew Wilcox
2005-05-15 17:57 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050515175730.GA3898@kroah.com \
--to=greg@kroah.com \
--cc=arjan@infradead.org \
--cc=gregkh@kroah.com \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=matthias.andree@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox