From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, siddhi.katage@oracle.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y 1/4] x86: Fix get_wchan() to support the ORC unwinder
Date: Wed, 23 Jul 2025 00:33:58 -0400 [thread overview]
Message-ID: <1753233242-65cf59f4@stable.kernel.org> (raw)
In-Reply-To: <20250722062642.309842-2-siddhi.katage@oracle.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found follow-up fixes in mainline
The upstream commit SHA1 provided is correct: bc9bbb81730ea667c31c5b284f95ee312bab466f
WARNING: Author mismatch between patch and upstream commit:
Backport author: Siddhi Katage <siddhi.katage@oracle.com>
Commit author: Qi Zheng <zhengqi.arch@bytedance.com>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (exact SHA1)
Found fixes commits:
5d1ceb3969b6 x86: Fix __get_wchan() for !STACKTRACE
Note: The patch differs from the upstream commit:
---
1: bc9bbb81730e ! 1: 1f7a2f87bdde x86: Fix get_wchan() to support the ORC unwinder
@@ Metadata
## Commit message ##
x86: Fix get_wchan() to support the ORC unwinder
+ [ Upstream commit bc9bbb81730ea667c31c5b284f95ee312bab466f ]
+
Currently, the kernel CONFIG_UNWINDER_ORC option is enabled by default
on x86, but the implementation of get_wchan() is still based on the frame
pointer unwinder, so the /proc/<pid>/wchan usually returned 0 regardless
@@ Commit message
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/20211008111626.271115116@infradead.org
+ Signed-off-by: Siddhi Katage <siddhi.katage@oracle.com>
## arch/x86/kernel/process.c ##
@@ arch/x86/kernel/process.c: unsigned long arch_randomize_brk(struct mm_struct *mm)
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| 5.15 | Success | Success |
next prev parent reply other threads:[~2025-07-23 4:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 6:26 [PATCH 5.15.y 0/4] Fix blank WHCAN value in 'ps' output Siddhi Katage
2025-07-22 6:26 ` [PATCH 5.15.y 1/4] x86: Fix get_wchan() to support the ORC unwinder Siddhi Katage
2025-07-23 4:33 ` Sasha Levin [this message]
2025-07-22 6:26 ` [PATCH 5.15.y 2/4] sched: Add wrapper for get_wchan() to keep task blocked Siddhi Katage
2025-07-23 4:33 ` Sasha Levin
2025-07-22 6:26 ` [PATCH 5.15.y 3/4] x86: Fix __get_wchan() for !STACKTRACE Siddhi Katage
2025-07-23 4:34 ` Sasha Levin
2025-07-22 6:26 ` [PATCH 5.15.y 4/4] x86: Pin task-stack in __get_wchan() Siddhi Katage
2025-07-23 4:34 ` Sasha Levin
2025-07-22 9:51 ` [PATCH 5.15.y 0/4] Fix blank WHCAN value in 'ps' output Greg KH
2025-07-22 11:13 ` [External] : " Siddhi Katage
2025-07-22 12:15 ` Greg KH
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=1753233242-65cf59f4@stable.kernel.org \
--to=sashal@kernel.org \
--cc=siddhi.katage@oracle.com \
--cc=stable@vger.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 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.