linux-kernel - Re: [PATCH] rtc-dev: stop periodic interrupts on device release

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:	Tue, 29 Jul 2008 01:36:38 +0200
From:	Tomáš Janoušek <tomi@...i.cz>
To:	David Brownell <david-b@...bell.net>
Cc:	linux-kernel@...r.kernel.org,
	Alessandro Zummo <alessandro.zummo@...ertech.it>
Subject: Re: [PATCH] rtc-dev: stop periodic interrupts on device release

Hello,

On Mon, Jul 28, 2008 at 03:05:36PM -0700, David Brownell wrote:
> Surely you agree that having the framework shut down only *emulated*
> update IRQs, not "real" ones, is inconsistent?  And hence undesirable?

The idea was that if the "real" ones get turned on using some ioctl magic the
framework has no exact control over, they shouldn't be shut down by it. But
yeah, your point of view looks fine as well.

So I guess I'll post the current patch to Andrew and then, someone (not me,
for time and competence reasons, sorry) can prepare a patch removing the
release op and changing the calls in framework's release to call
rtc_dev_ioctl.

Is this ok?

-- 
Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/
--
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/