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: <20090423212639.7ba7cb0b@i1501.lan.towertech.it>
Date:	Thu, 23 Apr 2009 21:26:39 +0200
From:	Alessandro Zummo <alessandro.zummo@...ertech.it>
To:	David Brownell <david-b@...bell.net>
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 Thu, 23 Apr 2009 12:25:01 -0700
David Brownell <david-b@...bell.net> wrote:

> >  but why rtc_update_irq should disable the IRQs? I believe
> >  it can work just fine with IRQs enabled.  
> 
> The last patch I saw was just changing from "caller must
> disable them" to "rtc_update_irq() disables them".
> 
> If you're talking about a different patch, please forward...

 no patch, just theory.

 the question is, do we need IRQs disabled when
 calling rtc_update_irq?

 and if yes, why? to prevent what?

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

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