From: Oleg Nesterov <oleg@redhat.com>
To: Andres Freund <andres@anarazel.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Evan Teran <eteran@alum.rit.edu>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
Pedro Alves <palves@redhat.com>,
Roland McGrath <roland@hack.frob.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ptrace/x86: fix the TIF_FORCED_TF logic in handle_signal()
Date: Mon, 23 Feb 2015 20:52:19 +0100 [thread overview]
Message-ID: <20150223195219.GA23937@redhat.com> (raw)
In-Reply-To: <20150217023157.GA2953@awork2.anarazel.de>
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.
next prev parent reply other threads:[~2015-02-23 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 20:12 [PATCH 0/1] ptrace/x86: fix the TIF_FORCED_TF logic in handle_signal() Oleg Nesterov
2014-11-03 20:13 ` [PATCH 1/1] " Oleg Nesterov
2014-11-03 21:40 ` Pedro Alves
2014-11-04 23:55 ` Oleg Nesterov
2014-11-05 9:57 ` Pedro Alves
2014-11-27 23:21 ` Oleg Nesterov
2015-02-17 2:31 ` Andres Freund
2015-02-23 19:52 ` Oleg Nesterov [this message]
2015-01-06 16:18 ` [PATCH RESEND] " Oleg Nesterov
2015-02-23 19:53 ` [PATCH 2nd " Oleg Nesterov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150223195219.GA23937@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andres@anarazel.de \
--cc=eteran@alum.rit.edu \
--cc=jan.kratochvil@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=palves@redhat.com \
--cc=roland@hack.frob.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.