From: Petr Mladek <pmladek@suse.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: x86@kernel.org, Dave Jones <davej@codemonkey.org.uk>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, live-patching@vger.kernel.org
Subject: Re: [PATCH 0/2] A couple of unwinder fixes
Date: Wed, 24 May 2017 13:47:08 +0200 [thread overview]
Message-ID: <20170524114708.GJ7297@pathway.suse.cz> (raw)
In-Reply-To: <cover.1495553739.git.jpoimboe@redhat.com>
On Tue 2017-05-23 10:37:28, Josh Poimboeuf wrote:
> Patch 1 reverts a previous fix because it introduced a new bug.
>
> Patch 2 re-fixes the original bug.
I could confirm that the new bug has gone after applying both
patches. Also I think that I have reproduced the original bug
and it seems to have gone as well. Therefore feel free to use
for both patches:
Tested-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
> Josh Poimboeuf (2):
> Revert "x86/entry: Fix the end of the stack for newly forked tasks"
> x86/unwind: Add end-of-stack check for ftrace handlers
>
> arch/x86/entry/entry_32.S | 30 ++++++++++++++++----------
> arch/x86/entry/entry_64.S | 11 ++++------
> arch/x86/kernel/unwind_frame.c | 49 ++++++++++++++++++++++++++++++++++--------
> 3 files changed, 63 insertions(+), 27 deletions(-)
>
> --
> 2.7.4
>
prev parent reply other threads:[~2017-05-24 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 15:37 Josh Poimboeuf
2017-05-23 15:37 ` [PATCH 1/2] Revert "x86/entry: Fix the end of the stack for newly forked tasks" Josh Poimboeuf
2017-05-24 10:16 ` [tip:x86/urgent] " tip-bot for Josh Poimboeuf
2017-05-23 15:37 ` [PATCH 2/2] x86/unwind: Add end-of-stack check for ftrace handlers Josh Poimboeuf
2017-05-24 10:17 ` [tip:x86/urgent] " tip-bot for Josh Poimboeuf
2017-05-24 11:47 ` Petr Mladek [this message]
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=20170524114708.GJ7297@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=davej@codemonkey.org.uk \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome