linux-kernel - Re: [PATCH] x86_64: fix delayed 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <alpine.LFD.1.10.0807101855020.2936@woody.linux-foundation.org>
Date:	Thu, 10 Jul 2008 19:02:25 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Roland McGrath <roland@...hat.com>
cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86_64: fix delayed signals

On Thu, 10 Jul 2008, Linus Torvalds wrote:
> 
> So the x86-64 behaviour actually matches what the x86-32 behavior was at 
> the time before things split.
> 
> And I'd also like to point out another commit, namely "[PATCH] fix broken 
> vm86 interrupt/signal handling" (4031ff388138b58e5cd472dccce38828bcb8c706) 
> that fixed a bug with an endless loop you had introduced in that original 
> x86-32 code when you fixed this exact same issue back when.
> 
> Heh. That's the kind of thing that worries me.

That said, seeing the full history of this same thing on the x86-32 side 
actually makes me _much_ happier about the patch. Because now I can tell 
when we did it, and what problems it seems to have caused (answer: 
"apparently none that are possibly relevant on x86-64").

IOW, just seeing the fact that we used to behave the same, and then 
changed it on the 32-bit side (with no apparent big issues) and did it 
without updating the 64-bit side, makes me just much happier about your 
patch. Just because I know know the background to why this was x86-64 
only.

So now I'm considering just putting it in before the 2.6.26 release after 
all ;)

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