From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 111241] New: one need root credentials to read cpuinfo_cur_freq content
Date: Sun, 24 Jan 2016 09:16:21 +0000 [thread overview]
Message-ID: <bug-111241-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=111241
Bug ID: 111241
Summary: one need root credentials to read cpuinfo_cur_freq
content
Product: Power Management
Version: 2.5
Kernel Version: 4.4.0-994-generic
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: flux242@gmail.com
Regression: No
could somebody explain why do I need root credentials to read cpuinfo_cur_freq
file? Why other files in the same directory have 444 and not 400 as the
cpuinfo_cur_freq? What so special about the current cpu freq readings?
$ lso /sys/devices/system/cpu/cpu?/cpufreq/cpuinfo*
400 -r-------- 1 root 4.0K Jan 24 09:30
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
444 -r--r--r-- 1 root 4.0K Jan 24 09:37
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
444 -r--r--r-- 1 root 4.0K Jan 24 09:37
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
444 -r--r--r-- 1 root 4.0K Jan 24 09:37
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency
400 -r-------- 1 root 4.0K Jan 24 09:53
/sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_cur_freq
444 -r--r--r-- 1 root 4.0K Jan 24 09:53
/sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_max_freq
444 -r--r--r-- 1 root 4.0K Jan 24 09:53
/sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_min_freq
444 -r--r--r-- 1 root 4.0K Jan 24 09:53
/sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_transition_latency
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2016-01-24 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 9:16 bugzilla-daemon [this message]
2016-01-24 16:33 ` [Bug 111241] one need root credentials to read cpuinfo_cur_freq content bugzilla-daemon
2016-01-24 17:09 ` bugzilla-daemon
2016-01-24 17:09 ` bugzilla-daemon
2016-05-16 21:47 ` bugzilla-daemon
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=bug-111241-137361@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-pm@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).