linux-kernel - Re: [PATCH] bitmap, irq: Add smp_affinity

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] [day] [month] [year] [list]

Date:	Thu, 31 Mar 2011 14:15:24 -0400
From:	Mike Frysinger <vapier.adi@...il.com>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Mike Travis <travis@....com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jack Steiner <steiner@....com>,
	Lee Schermerhorn <lee.schermerhorn@...com>,
	Andy Shevchenko <andy.shevchenko@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] bitmap, irq: Add smp_affinity_list interface to /proc/irq

On Thu, Mar 31, 2011 at 03:37, KOSAKI Motohiro wrote:
>> > [If it was up to me, I'd eliminate the bitmask interfaces and just keep the
>> > list interfaces.  That's the stupid interface that's not needed, and far more
>> > shortsighted.]
>>
>> Agree.
>>
>> It's not impossible to remove those interfaces.  My preferred approach
>> is to add a once-per-boot warning printk if anyone uses the old
>> interface and to remove the thing altogether in three or five years.
>>
>> That reminds me.  It's been like ten years.  Someone please delete sys_bdflush().
>
> This?
>
> But to be honest, this long diffstat seems tell me the worth is doubious. ;-)

you dont need to update the arches.  just leave the compat option in
kernel/sys_ni.c.  there is really no overhead at runtime as the func
is aliased to the ENOSYS stub.
-mike
--
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/