linux-kernel - Re: [RFC][PATCH 0/5] Signal scalability series

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: <1317461738.3375.46.camel@mfleming-mobl1.ger.corp.intel.com>
Date:	Sat, 01 Oct 2011 10:35:38 +0100
From:	Matt Fleming <matt@...sole-pimps.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Oleg Nesterov <oleg@...hat.com>, Tejun Heo <tj@...nel.org>,
	linux-kernel@...r.kernel.org, Tony Luck <tony.luck@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	David Mosberger-Tang <davidm@...uge.net>
Subject: Re: [RFC][PATCH 0/5] Signal scalability series

On Fri, 2011-09-30 at 15:30 -0700, Andi Kleen wrote:
> Matt Fleming <matt@...sole-pimps.org> writes:
> >
> > And just like last time, these patches break ia64 because it
> > implements rt_sigprocmask() in assembly. I'll work on the ia64 stuff
> > while these patches are being reviewed.
> 
> Since we don't want to tie everyone changing signals in the future to
> learning IA64 assembler, maybe the best approach would be simply to
> change that function to just use the syscall. It can't be that
> performance critical and everyone else has it as a syscall too.
> 
> I think that would be the best solution for long term maintainability.

You and me both. Unfortunately, the ia64 guys had a different opinion,
http://www.spinics.net/lists/linux-ia64/msg08363.html

-- 
Matt Fleming, Intel Open Source Technology Center

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