linux-kernel - Re: [PATCH] RTC: Add an alarm disable quirk

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]

Date:	Mon, 22 Jul 2013 14:15:57 -0700
From:	John Stultz <john.stultz@...aro.org>
To:	Borislav Petkov <bp@...en8.de>
CC:	LKML <linux-kernel@...r.kernel.org>, Jiri Kosina <jkosina@...e.cz>,
	Borislav Petkov <bp@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Rabin Vincent <rabin.vincent@...ricsson.com>
Subject: Re: [PATCH] RTC: Add an alarm disable quirk

On 07/22/2013 02:12 PM, Borislav Petkov wrote:
> On Mon, Jul 22, 2013 at 01:59:01PM -0700, John Stultz wrote:
>> So did this work some of the time, but not all? Or was the behavior
>> totally unchanged with this?
> Yep, some of the time. The first couple of runs it worked and I was
> euphoric and then it rebooted and I almost threw the box out the window
> :-)

I can understand your frustration. :)

But its interesting it sort of worked, no?  The bit you discovered 
earlier with the dump_stack debugging call, where we're actually 
disabling the irq twice was interesting.

If you use the debugging patch with this change, does it show any 
different in logic between the working cases and the instant-reboot case?

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/