| 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
| ||
|
Date: Fri, 26 Apr 2013 01:22:56 +0200 From: Kay Sievers <kay@...y.org> To: John Stultz <john.stultz@...aro.org> Cc: lkml <linux-kernel@...r.kernel.org>, stable <stable@...r.kernel.org>, Feng Tang <feng.tang@...el.com>, Jason Gunthorpe <jgunthorpe@...idianresearch.com>, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [PATCH] time: Revert ALWAYS_USE_PERSISTENT_CLOCK compile time optimizaitons On Wed, Apr 24, 2013 at 8:55 PM, John Stultz <john.stultz@...aro.org> wrote: >> FWIW, in the light of the original change, I've just removed the >> /dev/rtc creation from the default udev rules now, so that thing will >> be phased out in the future. > > Is that actually wanted? What happens to applications that use /dev/rtc? > > I think setting up the /dev/rtc link is important. Its just that setting it > up exclusively by the hctosys flag is maybe more fragile then we'd like. > Instead the hctosys flag maybe should only be used as a hint if there is > more then one RTC available. Ok, convinced. I've changed the udev rules now to first "search" for the rtc with "hctosys" flag set, and if none is found, just fall back to /dev/rtc0. It should work reliably on most boxes, and still do the right thing in most cases if none of the rtcs has that flag. Thanks, Kay -- 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/
Powered by blists - more mailing lists