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: <200904240410.52543.david-b@pacbell.net>
Date:	Fri, 24 Apr 2009 04:10:51 -0700
From:	David Brownell <david-b@...bell.net>
To:	Alessandro Zummo <alessandro.zummo@...ertech.it>
Cc:	rtc-linux@...glegroups.com, Atsushi Nemoto <anemo@....ocn.ne.jp>,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	hcegtvedt@...el.com, vapier@...too.org, rongkai.zhan@...driver.com,
	balajirrao@...nmoko.org, broonie@...nsource.wolfsonmicro.com
Subject: Re: [rtc-linux] Re: [PATCH] rtc: Make rtc_update_irq callable with irqs enabled

On Friday 24 April 2009, Alessandro Zummo wrote:
>  I'm not tying to fix call issues or lockdep politics,
>  just to understand if it's possible to avoid disabling the IRQs.
> 
>  i.e.,
> 
>  use spin_lock() in the IRQ handler and spin_lock_irq/irq_save
>  in the setup functions.

I think you're describing how the *current* scheme is supposed
to work ... except that some IRQ handlers aren't calling the
rtc_update_irq() routine with IRQs blocked.

Yes, that current scheme works ... modulo those buggy handlers.


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