linux-kernel - Re: [PATCH 2.6.21-rc1] x86 signal number delivery fixes

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]

Message-Id: <200702252339.48933.ak@suse.de>
Date:	Sun, 25 Feb 2007 23:39:48 +0100
From:	Andi Kleen <ak@...e.de>
To:	Mikael Pettersson <mikpe@...uu.se>
Cc:	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.21-rc1] x86 signal number delivery fixes

On Sunday 25 February 2007 12:47, Mikael Pettersson wrote:
> The invokation of signal handlers on x86 has several bugs
> in its treatment of the signal number parameter:
> 
> - the i386 kernel passes the raw not the translated signal number
>   in EAX to non-SA_SIGINFO handlers compiled with -mregparm=3;
>   the value passed on the stack is correct, and SA_SIGINFO handlers
>   are also invoked correctly
> - the x86-64 kernel's ia32 emulation for SA_SIGINFO handlers also
>   passes the wrong (untranslated) signal number in EAX; the value
>   on the stack is correct
> - the x86-64 kernel's ia32 emulation for non-SA_SIGINFO handlers
>   passes the wrong (untranslated) signal number both on the stack 
>   and in EAX


Nobody should be using that signal translation code anymore. Certainly
nothing in tree. Perhaps it would be better to just rip it out.

If you have a user you should submit it.

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