From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
John Stultz <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clocksource: Fix permissions for available_clocksource
Date: Sat, 3 May 2008 14:23:14 +0200 [thread overview]
Message-ID: <20080503122314.GA5996@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0805021731550.6003@apollo.tec.linutronix.de>
On Fri, May 02, 2008 at 05:34:06PM +0200, Thomas Gleixner wrote:
> On Fri, 2 May 2008, Heiko Carstens wrote:
> > On Fri, May 02, 2008 at 04:36:37PM +0200, Thomas Gleixner wrote:
> > > On Fri, 2 May 2008, Heiko Carstens wrote:
> > > > From: Heiko Carstens <heiko.carstens@de.ibm.com>
> > > >
> > > > File permissions for
> > > > /sys/devices/system/clocksource/clocksource0/available_clocksource
> > > > are 600 which allows write access. But this is in fact a read only
> > > > file. So change permissions to 400.
> > >
> > > Indeed. The question is whether we should make this 444. There is no
> > > harm, when users can read the info. Same applies for the
> > > current_clocksource entry, making it 644 should be fine.
> >
> > Sure, I can send an on-top patch for this.
>
> Yes, please.
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
---
kernel/time/clocksource.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: linux-2.6/kernel/time/clocksource.c
===================================================================
--- linux-2.6.orig/kernel/time/clocksource.c
+++ linux-2.6/kernel/time/clocksource.c
@@ -471,10 +471,10 @@ sysfs_show_available_clocksources(struct
/*
* Sysfs setup bits:
*/
-static SYSDEV_ATTR(current_clocksource, 0600, sysfs_show_current_clocksources,
+static SYSDEV_ATTR(current_clocksource, 0644, sysfs_show_current_clocksources,
sysfs_override_clocksource);
-static SYSDEV_ATTR(available_clocksource, 0400,
+static SYSDEV_ATTR(available_clocksource, 0444,
sysfs_show_available_clocksources, NULL);
static struct sysdev_class clocksource_sysclass = {
next prev parent reply other threads:[~2008-05-03 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 10:49 Heiko Carstens
2008-05-02 14:36 ` Thomas Gleixner
2008-05-02 15:27 ` Heiko Carstens
2008-05-02 15:34 ` Thomas Gleixner
2008-05-03 12:23 ` Heiko Carstens [this message]
2008-05-02 18:31 ` john stultz
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=20080503122314.GA5996@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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
Powered by JetHome