linux-kernel - Re: [RFC] x86, fpu: unify signal handling code paths for x86 and x86

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: <4FDA7EDE.3070408@zytor.com>
Date:	Thu, 14 Jun 2012 17:16:30 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Suresh Siddha <suresh.b.siddha@...el.com>
CC:	Hans Rosenfeld <hans.rosenfeld@....com>,
	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>, tglx@...utronix.de,
	robert.richter@....com, andreas.herrmann3@....com
Subject: Re: [RFC] x86, fpu: unify signal handling code paths for x86 and
 x86_64 kernels

On 06/14/2012 05:10 PM, Suresh Siddha wrote:
> 
> For the above mentioned reason, I guess the current usage of
> is_ia32_task() in copy_siginfo_to_user32() (added recently for x32
> support) is broken, as the TS_COMPAT flag may not be set for the x86
> compat mode apps in those paths.
> 
> Peter offline suggested that the signal  delivery path should probably
> set/clear the TS_COMPAT flag (just like we do it for syscall paths), so
> that is_ia32_task() will work in those paths.
> 
> But the exception paths for the 32bit and 64bit apps in the 64-bit
> kernel is same. So I really need to use something like TIF_IA32 to find
> out the compat mode of the task. Anyways, the comment in the below patch
> explains the problem ;) What should we do? Just remove the
> is_ia32_task() checks in signal paths and just use TIF_IA32 or do
> something like below.
> 
> My personal preference is to use TIF_IA32 check and avoid  the usage of
> is_ia32_task() in the signal delivery paths.

That is the quick fix, but...

> Signal return goes through a system call which already sets the
> TS_COMPAT. It is the signal delivery that is causing the asymmetry.

Yes, and I think you missed some aspects of my statement: the notion
would be that TS_COMPAT would be set from the TIF_IA32 flag at the time
we decide to deliver a signal, the signal being a pseudo-system-call.
However, the more I wonder about if that will confuse the crap out of
ptrace, so using TIF_IA32 might just be the best thing anyway.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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