linux-kernel - Re: [PATCH 00/16] dyn_array and nr

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:	Sat, 02 Aug 2008 08:41:03 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
CC:	Yinghai Lu <yhlu.kernel@...il.com>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
	Mike Travis <travis@....com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/16] dyn_array and nr_irqs support v2

Eric W. Biederman wrote:
> 
> Yes.  I want the option of using those bits.  It might not be smart to
> use them to encode a physical location and the irq number but just
> having the option would be nice.
> 

Urk!  First of all, there isn't enough space as we have already proven 
(on the machines where it actually matters there just aren't enough 
bits), but doing this kind of stuff *optionally* is going to hurt even 
worse.

Furthermore, this crap will break anyway the *next* time someone comes 
up with a new clever way to do interrupts -- and to truly get stable 
identifiers, we can't treat HyperTransport MSI as APICs anymore, yadda, 
yadda...

> Making /proc/interrupts useful without breaking user space is going to be
> an interesting challenge one of these days.

If changing to non-numbers in /proc/interrupts will break userspace, 
then userspace will have to deal with a numeric token in 
/proc/interrupts which will have to be looked up elsewhere (perhaps in a 
sysfs directory) to get a more meaningful index.

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