linux-kernel - Re: [PATCHv1 11/12] unicore32 core architecture: signals

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 7 Jan 2011 01:16:57 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	"Guan Xuetao" <guanxuetao@...c.pku.edu.cn>,
	Al Viro <viro@....linux.org.uk>
Cc:	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv1 11/12] unicore32 core architecture: signals

On Saturday 25 December 2010, Guan Xuetao wrote:
> From: Guan Xuetao <guanxuetao@...c.pku.edu.cn>
> 
> Patch 11 implements signals.
> 
> Signed-off-by: Guan Xuetao <guanxuetao@...c.pku.edu.cn>
> ---
>  arch/unicore32/include/asm/sigcontext.h |   61 ++++
>  arch/unicore32/kernel/signal.c          |  571 +++++++++++++++++++++++++++++++
>  arch/unicore32/kernel/signal.h          |   16 +
>  3 files changed, 648 insertions(+), 0 deletions(-)

Al Viro recently did a major cleanup of the signal handling code in a
number of architectures. He can probably give much better feedback
on this one than I can.

The one thing that sticks out to me is that you implement both legacy
and rt signals, where new architectures should generally only need the
rt variant.

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