linux-kernel - Re: [PATCH] clocksource: Fix permissions for available

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080502152730.GA5220@osiris.boeblingen.de.ibm.com>
Date:	Fri, 2 May 2008 17:27:30 +0200
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	John Stultz <johnstul@...ibm.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] clocksource: Fix permissions for available_clocksource

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@...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.

Btw. did you recently try writing "jiffies" to current_clocksource?
That seems to be a trick to stop the clock...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/