linux-kernel - Re: [PATCH 1/1] ptrace/x86: fix the TIF_FORCED_TF logic in handle

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 Feb 2015 20:52:19 +0100
From:	Oleg Nesterov <oleg@...hat.com>
To:	Andres Freund <andres@...razel.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Evan Teran <eteran@...m.rit.edu>,
	Jan Kratochvil <jan.kratochvil@...hat.com>,
	Pedro Alves <palves@...hat.com>,
	Roland McGrath <roland@...k.frob.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] ptrace/x86: fix the TIF_FORCED_TF logic in
	handle_signal()

On 02/17, Andres Freund wrote:
>
> Could this patch please be picked up? I very regularly hit the problems
> caused due to this in gdb (just single step out of a system call that
> returns due to EINTR to reproduce and then single step some more...).
>
> I've first spent an embarassing amount of time trying to figure out
> what's wrong, to then find a closed bugzilla entry from 2010, to then
> find this thread...
>
> I've verified that applying the fix ontop 1fa185ebcbc fixes the issue
> for me. So feel free to add a Tested-By. I, by far, don't understand the
> code well enough for an actual review though, sorry.
>
> Anything else I can do?

Lets hope your tested-by will help ;) I'll resend this fix once again.

Oleg.

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