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: <1321993924.6445.74.camel@work-vm>
Date:	Tue, 22 Nov 2011 12:32:04 -0800
From:	John Stultz <john.stultz@...aro.org>
To:	Linus Walleij <linus.walleij@...ricsson.com>
Cc:	Alessandro Zummo <a.zummo@...ertech.it>,
	rtc-linux@...glegroups.com, linux-kernel@...r.kernel.org,
	Rabin Vincent <rabin.vincent@...ricsson.com>, stable@...nel.org
Subject: Re: [PATCH] rtc: disable the alarm in the hardware

On Tue, 2011-11-22 at 11:03 +0100, Linus Walleij wrote:
> From: Rabin Vincent <rabin.vincent@...ricsson.com>
> 
> Currently, the RTC code does not disable the alarm in the hardware.
> 
> This means that after a sequence such as the one below (the files are in the
> RTC sysfs), the box will boot up after 2 minutes even though we've
> asked for the alarm to be turned off.
> 
> 	# echo $((`cat since_epoch`)+120) > wakealarm
> 	# echo 0 > wakealarm
> 	# poweroff
> 
> Fix this by disabling the alarm when there are no timers to run.

Hey Linus,
	Thanks for sending this along! It looks like a good fix to me! I'm a
little amazed this hasn't cropped up sooner.  I'll do some further
testing and then queue it for upstream.

thanks
-john


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

Powered by Openwall GNU/*/Linux Powered by OpenVZ