From: Guoheyi <guoheyi@huawei.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mike Waychison <mikew@google.com>, <linux-kernel@vger.kernel.org>,
wanghaibin 00208455 <wanghaibin.wang@huawei.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: firmware: dmi-sysfs: why is the access mode of dmi sysfs entries restricted to 0400?
Date: Fri, 6 Dec 2019 10:04:31 +0800 [thread overview]
Message-ID: <b75e2aac-e27c-8d26-36c7-6fb69b769bbd@huawei.com> (raw)
In-Reply-To: <20191204092942.GA3557583@kroah.com>
在 2019/12/4 17:29, Greg Kroah-Hartman 写道:
> On Wed, Dec 04, 2019 at 05:01:06PM +0800, Guoheyi wrote:
>> 在 2019/12/4 15:41, Greg Kroah-Hartman 写道:
>>> On Wed, Dec 04, 2019 at 03:31:22PM +0800, Guoheyi wrote:
>>>> Hi,
>>>>
>>>> Why is the access mode of dmi sysfs entries restricted to 0400? Is it for
>>>> security concern? If it is, which information do we consider as privacy?
>>> There's lots of "interesting" information in dmi entries that you
>>> probably do not want all processes reading, which is why they are
>>> restricted.
>>>
>>>> We would like to fetch CPU information from non-root application, is there
>>>> feasible way to do that?
>>> What specific CPU information is not currently exported in /proc/cpuinfo
>>> that only shows up in DMI entries that you are interested in?
>> We'd like to get processor manufacturer, speed and version, and pass the
>> information to qemu virtual machine, for users of VM might be happy to see
>> this instead of "unknown xxx", while qemu may run as non-root.
> Careful about this as if you move that virtual machine around, those
> values will change and if userspace was depending on them being static
> (set up at program start time), then you might have problems.
>
> good luck!
The information will be used as VM DMI/SMBIOS as well, so it will be
read only once during VM boot. I guess we will be OK :)
Thanks a lot.
Heyi
>
> greg k-h
>
> .
prev parent reply other threads:[~2019-12-06 2:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 7:31 Guoheyi
2019-12-04 7:41 ` Greg Kroah-Hartman
2019-12-04 9:01 ` Guoheyi
2019-12-04 9:29 ` Greg Kroah-Hartman
2019-12-06 2:04 ` Guoheyi [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=b75e2aac-e27c-8d26-36c7-6fb69b769bbd@huawei.com \
--to=guoheyi@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=tglx@linutronix.de \
--cc=wanghaibin.wang@huawei.com \
/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
all inboxes | Powered by JetHome®