From: Dave Jones <davej@redhat.com>
To: Dan Hollis <goemon@anime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bizarre 2.6.8.1 /sys permissions
Date: Wed, 25 Aug 2004 23:18:14 +0100 [thread overview]
Message-ID: <20040825221814.GA20283@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0408251319070.4007-100000@sasami.anime.net>
On Wed, Aug 25, 2004 at 01:25:12PM -0700, Dan Hollis wrote:
> Do these file permissions make sense to anyone?
Yes.
> $ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
> cat: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq: Permission denied
Reading this file causes reads from hardware on some cpufreq drivers.
This can be a slow operation, so a user could degrade system performance
for everyone else by repeatedly cat'ing it.
> $ cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 15
> model : 2
> model name : Intel(R) Celeron(R) CPU 2.60GHz
> stepping : 9
> cpu MHz : 324.528
This is read from the cpu_khz variable, so isn't affected by
this problem.
> $ ls -la /sys/devices/system/cpu/cpu0/cpufreq/
> total 0
> drwxr-xr-x 2 root root 0 Aug 23 13:06 .
> drwxr-xr-x 3 root root 0 Aug 23 13:06 ..
> -r-------- 1 root root 4096 Aug 23 13:06 cpuinfo_cur_freq
> -r--r--r-- 1 root root 4096 Aug 23 13:06 cpuinfo_max_freq
> -r--r--r-- 1 root root 4096 Aug 23 13:06 cpuinfo_min_freq
> -r--r--r-- 1 root root 4096 Aug 23 13:06 scaling_available_frequencies
> -r--r--r-- 1 root root 4096 Aug 23 13:06 scaling_available_governors
> -r--r--r-- 1 root root 4096 Aug 23 13:06 scaling_cur_freq
> -r--r--r-- 1 root root 4096 Aug 23 13:06 scaling_driver
> -rw-r--r-- 1 root root 0 Aug 25 13:19 scaling_governor
> -rw-r--r-- 1 root root 4096 Aug 23 13:06 scaling_max_freq
> -rw-r--r-- 1 root root 4096 Aug 23 13:06 scaling_min_freq
> -rw-r--r-- 1 root root 0 Aug 25 13:19 scaling_setspeed
Looks fine to me.
Dave
next prev parent reply other threads:[~2004-08-25 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 20:25 bizarre 2.6.8.1 /sys permissions Dan Hollis
2004-08-25 22:18 ` Dave Jones [this message]
2004-08-25 23:31 ` Dan Hollis
2004-08-26 0:48 ` Dave Jones
2004-08-26 19:00 ` Bill Davidsen
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=20040825221814.GA20283@redhat.com \
--to=davej@redhat.com \
--cc=goemon@anime.net \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.