linux-kernel - Re: [git patch] free

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: <m11w4u8x1c.fsf@frodo.ebiederm.org>
Date:	Thu, 24 Apr 2008 19:53:51 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Rene Herman <rene.herman@...access.nl>,
	Adrian Bunk <bunk@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, rmk@....linux.org.uk,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>
Subject: Re: [git patch] free_irq() fixes

Jeff Garzik <jeff@...zik.org> writes:

> Eric W. Biederman wrote:
>> And on x86 at least the hardware maps the MSI write into an interrupt.
>> So there is not an opportunity to get any metdata/OOB data from the
>> MSI message.  Instead we just potentially get a boatload more irq
>> sources.  Which is one of the things making a static NR_IRQS painful.
>>
>> To be safe we have to make NR_IRQS 10x+ or so bigger then people use
>> today.  Just in case they decide to plug in some really irq hungry
>> cards.
>
>
> Just to be clear, irq_chip/irq_desc and metadata/OOB data are two very different
> beasts.  irq_chip/irq_desc is more a system attribute as Linus notes.  Also, it
> doesn't change very often.
>
> metadata/OOB, on the other hand, is different -for each interrupt-, and is
> highly relevant to drivers.  Thus should be part of the driver API somehow.

I'm not certain I follow so I will ask.

Do you mean information that is different each time an interrupt is fires?

Or do you mean information that differs for each different interrupt?
Something like the current dev_id?

To my knowledge there is not any information that varies each time an
interrupt fires.

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