linux-kernel - Re: [PATCH] genirq: do not mask interrupts by default

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, 27 Mar 2007 09:32:27 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	Andrew Morton <akpm@...l.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Paul Mackerras <paulus@...ba.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...l.org>
Subject: Re: [PATCH] genirq: do not mask interrupts by default

* Benjamin Herrenschmidt <benh@...nel.crashing.org> wrote:

> Note that I'm not opposed to the change at all, I think it's a good 
> idea, I'm just worried I'm discovering it a bit late and I've seen 
> PICs broken in some many colorful ways that I'm a bit worried... Oh 
> well...

This change does not really change irq-flow semantics, what it does is 
that disable_irq()'s effect is delayed. The irq controller does not have 
to re-assert the irq, we've got the soft-resend mechanism. What am i 
missing? Are you worried about this change causing actual breakage? (and 
i'm sorry about not having Cc:-ed you explicitly, i could have sworn you 
were included in that discussion but apparently not!)

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