From: Peter Zijlstra <peterz@infradead.org>
To: Qi Zheng <zhengqi.arch@bytedance.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Holger Hoffst??tte <holger@applied-asynchrony.com>,
Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Justin Forbes <jmforbes@linuxtx.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>, Shuah Khan <shuah@kernel.org>,
patches@kernelci.org, lkft-triage@lists.linaro.org,
Pavel Machek <pavel@denx.de>, Jon Hunter <jonathanh@nvidia.com>,
Florian Fainelli <f.fainelli@gmail.com>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] x86: Pin task-stack in __get_wchan()
Date: Fri, 19 Nov 2021 11:22:49 +0100 [thread overview]
Message-ID: <YZd6+SFZVzTeX45f@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <759cd319-990f-af23-2f1c-aba55d0768b8@bytedance.com>
On Fri, Nov 19, 2021 at 06:02:50PM +0800, Qi Zheng wrote:
> This implementation is very similar to stack_trace_save_tsk(), maybe we
> can just move stack_trace_save_tsk() out of CONFIG_STACKTRACE and reuse
> it.
No, we want to move away from the stack_trace_*() API because it has
very unclear semantics and various arch implementations differ in
details.
There's a patch that untangles arch_stack_walk*() from CONFIG_STACKTRACE
and we can eventually use that.
next prev parent reply other threads:[~2021-11-19 10:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 10:19 [PATCH 5.15 000/923] 5.15.3-rc3 review Greg Kroah-Hartman
2021-11-17 13:37 ` Fox Chen
2021-11-17 14:13 ` Guenter Roeck
2021-11-17 14:43 ` Greg Kroah-Hartman
2021-11-17 14:54 ` Guenter Roeck
2021-11-17 17:34 ` Jon Hunter
2021-11-17 18:51 ` Florian Fainelli
2021-11-17 20:25 ` Holger Kiehl
2021-11-18 8:14 ` Greg Kroah-Hartman
2021-11-18 14:08 ` Holger Kiehl
2021-11-18 17:08 ` Greg Kroah-Hartman
2021-11-17 20:35 ` Guenter Roeck
2021-11-17 21:32 ` Justin Forbes
2021-11-17 23:32 ` Holger Hoffstätte
2021-11-17 23:50 ` Linus Torvalds
2021-11-18 0:16 ` Kees Cook
2021-11-18 6:26 ` Guenter Roeck
2021-11-18 8:14 ` Greg Kroah-Hartman
2021-11-18 8:12 ` Greg Kroah-Hartman
2021-11-18 17:17 ` Kees Cook
2021-11-18 8:06 ` Peter Zijlstra
2021-11-18 8:18 ` Peter Zijlstra
2021-11-18 9:39 ` Peter Zijlstra
2021-11-18 10:12 ` Peter Zijlstra
2021-11-18 12:11 ` Peter Zijlstra
2021-11-19 2:04 ` Josh Poimboeuf
2021-11-19 9:29 ` [PATCH] x86: Pin task-stack in __get_wchan() Peter Zijlstra
2021-11-19 10:02 ` Qi Zheng
2021-11-19 10:22 ` Peter Zijlstra [this message]
2021-11-19 10:26 ` Qi Zheng
2021-11-19 18:16 ` Linus Torvalds
2021-11-19 18:35 ` Josh Poimboeuf
2021-11-22 9:32 ` Peter Zijlstra
2021-11-22 16:14 ` Josh Poimboeuf
2021-11-18 5:45 ` [PATCH 5.15 000/923] 5.15.3-rc3 review Naresh Kamboju
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=YZd6+SFZVzTeX45f@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=holger@applied-asynchrony.com \
--cc=jmforbes@linuxtx.org \
--cc=jonathanh@nvidia.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=zhengqi.arch@bytedance.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;
as well as URLs for NNTP newsgroup(s).