From: Sergei Trofimovich <slyfox@gentoo.org>
To: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2, simpler] ia64: fix ptrace(PTRACE_GETREGS) (unbreaks strace, gdb)
Date: Sat, 04 Aug 2018 21:33:36 +0000 [thread overview]
Message-ID: <20180804223336.5f29778e@sf> (raw)
In-Reply-To: <20180309231555.16925-1-slyfox@gentoo.org>
On Fri, 9 Mar 2018 23:15:55 +0000
Sergei Trofimovich <slyfox@gentoo.org> wrote:
I tried to explain in more detail breakage mechanics
of unwinder and gcc code generation quirks at:
https://trofi.github.io/posts/210-ptrace-and-accidental-boot-fix-on-ia64.html
Hopefully it gives better intuition of code change
caused by both proposed patches.
I personally think v1 patch is slightly more robust.
--
Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Trofimovich <slyfox@gentoo.org>
To: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2, simpler] ia64: fix ptrace(PTRACE_GETREGS) (unbreaks strace, gdb)
Date: Sat, 4 Aug 2018 22:33:36 +0100 [thread overview]
Message-ID: <20180804223336.5f29778e@sf> (raw)
In-Reply-To: <20180309231555.16925-1-slyfox@gentoo.org>
On Fri, 9 Mar 2018 23:15:55 +0000
Sergei Trofimovich <slyfox@gentoo.org> wrote:
I tried to explain in more detail breakage mechanics
of unwinder and gcc code generation quirks at:
https://trofi.github.io/posts/210-ptrace-and-accidental-boot-fix-on-ia64.html
Hopefully it gives better intuition of code change
caused by both proposed patches.
I personally think v1 patch is slightly more robust.
--
Sergei
next prev parent reply other threads:[~2018-08-04 21:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 22:12 [PATCH] ia64: fix ptrace(PTRACE_GETREGS) (unbreaks strace, gdb) Sergei Trofimovich
2018-02-02 22:12 ` Sergei Trofimovich
2018-02-02 22:22 ` Luck, Tony
2018-02-02 22:22 ` Luck, Tony
2018-02-02 23:02 ` Sergei Trofimovich
2018-02-02 23:02 ` Sergei Trofimovich
2018-02-11 18:51 ` Sergei Trofimovich
2018-03-09 23:15 ` [PATCH v2, simpler] " Sergei Trofimovich
2018-03-09 23:15 ` Sergei Trofimovich
2018-08-04 21:33 ` Sergei Trofimovich [this message]
2018-08-04 21:33 ` Sergei Trofimovich
2019-04-29 10:38 ` [PATCH] " John Paul Adrian Glaubitz
2019-04-29 10:38 ` John Paul Adrian Glaubitz
2019-04-29 11:34 ` John Paul Adrian Glaubitz
2019-04-29 11:34 ` John Paul Adrian Glaubitz
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=20180804223336.5f29778e@sf \
--to=slyfox@gentoo.org \
--cc=fenghua.yu@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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.