linux-kernel - Re: [PATCH] irq: handle irq0 special only on x86

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: <20091209.014151.140337246.davem@davemloft.net>
Date:	Wed, 09 Dec 2009 01:41:51 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	xiyou.wangcong@...il.com
Cc:	u.kleine-koenig@...gutronix.de, x86@...nel.org,
	linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
	hpa@...or.com
Subject: Re: [PATCH] irq: handle irq0 special only on x86

From: Am.$(D+1.(Brico Wang <xiyou.wangcong@...il.com>
Date: Wed, 9 Dec 2009 17:28:09 +0800

> 2009/12/9 Uwe Kleine-K.$(D+S.(Bnig <u.kleine-koenig@...gutronix.de>:
>> I just noticed this when digging in the irq handling. .,A .(BAt least for arm
>> this doesn't make sense. .,A .(BNot sure if x86 is the only arch this test
>> is valid for, but probably it is.
> 
> No, it is not.
> 
> Try grep -Inr 'irq0' arch/*/kernel.

The edict was sent down long ago that IRQ number zero is
special across the entire kernel tree.

If IRQ zero can happen, you should offset the IRQ values you publish
to the rest of the kernel, and translate them back when you process
them internally.
--
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/