public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Riesen <Alexander.Riesen@synopsys.com>
To: Ingo Molnar <mingo@redhat.com>
Cc: Alex Riesen <Alexander.Riesen@synopsys.COM>,
	linux-kernel@vger.kernel.org
Subject: Re: world read permissions on /proc/irq/prof_cpu_mask and ...smp_affinity
Date: Wed, 4 Dec 2002 19:19:00 +0100	[thread overview]
Message-ID: <20021204181900.GF26745@riesen-pc.gr05.synopsys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0212041036001.22730-100000@devserv.devel.redhat.com>

On Wed, Dec 04, 2002 at 10:37:01AM -0500, Ingo Molnar wrote:
> > Is there any reason to set the permissions to 0600?
> > It makes the admin to login as root just to look on the
> > current system state.
> > Is there something against 0644?
> 
> i've got nothing against 0644, 0600 was just the default paranoid value.  
> (reading it could in theory mean an IO-APIC read.)

The some objections against it (in vein: most people who want to
read it, supposed to want write into it).

But as for now it seems to be the only reason to have it readable
(and such things as /proc/ide/ideN/hdX/settings) is pure curiousity:
i don't really like to bother usually overworked admin to look at the
prof_cpu_mask just to figure out why all interrupts handled by CPU0.
And he is supposed to deny any my attempts to get root-SUID cat :)

-alex

  reply	other threads:[~2002-12-04 18:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 11:49 world read permissions on /proc/irq/prof_cpu_mask and ...smp_affinity Alex Riesen
2002-12-04 15:37 ` Ingo Molnar
2002-12-04 18:19   ` Alex Riesen [this message]
2002-12-05 11:24   ` Alex Riesen

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=20021204181900.GF26745@riesen-pc.gr05.synopsys.com \
    --to=alexander.riesen@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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