From: Josh Poimboeuf <jpoimboe@redhat.com>
To: "Wangshaobo (bobo)" <bobo.shaobowang@huawei.com>
Cc: huawei.libin@huawei.com, xiexiuqi@huawei.com,
cj.chengjian@huawei.com, mingo@redhat.com, x86@kernel.org,
linux-kernel@vger.kernel.org, live-patching@vger.kernel.org,
mbenes@suse.cz, devel@etsukata.com, viro@zeniv.linux.org.uk,
esyr@redhat.com
Subject: Re: Question: livepatch failed for new fork() task stack unreliable
Date: Tue, 2 Jun 2020 08:14:50 -0500 [thread overview]
Message-ID: <20200602131450.oydrydelpdaval4h@treble> (raw)
In-Reply-To: <a5e0f476-02b5-cc44-8d4e-d33ff2138143@huawei.com>
On Tue, Jun 02, 2020 at 09:22:30AM +0800, Wangshaobo (bobo) wrote:
> so i think this question is related to ORC unwinder, could i ask if you have
> strategy or plan to avoid this problem ?
I suspect something like this would fix it (untested):
diff --git a/arch/x86/kernel/stacktrace.c b/arch/x86/kernel/stacktrace.c
index 6ad43fc44556..8cf95ded1410 100644
--- a/arch/x86/kernel/stacktrace.c
+++ b/arch/x86/kernel/stacktrace.c
@@ -50,7 +50,7 @@ int arch_stack_walk_reliable(stack_trace_consume_fn consume_entry,
if (regs) {
/* Success path for user tasks */
if (user_mode(regs))
- return 0;
+ break;
/*
* Kernel mode registers on the stack indicate an
@@ -81,10 +81,6 @@ int arch_stack_walk_reliable(stack_trace_consume_fn consume_entry,
if (unwind_error(&state))
return -EINVAL;
- /* Success path for non-user tasks, i.e. kthreads and idle tasks */
- if (!(task->flags & (PF_KTHREAD | PF_IDLE)))
- return -EINVAL;
-
return 0;
}
diff --git a/arch/x86/kernel/unwind_orc.c b/arch/x86/kernel/unwind_orc.c
index 7f969b2d240f..d7396431261a 100644
--- a/arch/x86/kernel/unwind_orc.c
+++ b/arch/x86/kernel/unwind_orc.c
@@ -540,7 +540,7 @@ bool unwind_next_frame(struct unwind_state *state)
state->sp = sp;
state->regs = NULL;
state->prev_regs = NULL;
- state->signal = false;
+ state->signal = ((void *)state->ip == ret_from_fork);
break;
case ORC_TYPE_REGS:
next prev parent reply other threads:[~2020-06-02 13:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 10:10 Question: livepatch failed for new fork() task stack unreliable Wang ShaoBo
2020-05-29 17:44 ` Josh Poimboeuf
[not found] ` <a9ed9157-f3cf-7d2c-7a8e-56150a2a114e@huawei.com>
2020-06-01 18:05 ` Josh Poimboeuf
2020-06-02 1:22 ` Wangshaobo (bobo)
2020-06-02 13:14 ` Josh Poimboeuf [this message]
2020-06-03 14:06 ` Wangshaobo (bobo)
2020-06-03 15:33 ` Josh Poimboeuf
2020-06-04 1:24 ` Wangshaobo (bobo)
2020-06-04 2:40 ` Josh Poimboeuf
2020-06-05 1:26 ` Wangshaobo (bobo)
2020-06-05 1:51 ` Josh Poimboeuf
2020-06-30 13:04 ` Wangshaobo (bobo)
2020-06-30 21:36 ` Josh Poimboeuf
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=20200602131450.oydrydelpdaval4h@treble \
--to=jpoimboe@redhat.com \
--cc=bobo.shaobowang@huawei.com \
--cc=cj.chengjian@huawei.com \
--cc=devel@etsukata.com \
--cc=esyr@redhat.com \
--cc=huawei.libin@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mingo@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.org \
--cc=xiexiuqi@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox