[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210929220218.691419-1-keescook@chromium.org>
Date: Wed, 29 Sep 2021 15:02:12 -0700
From: Kees Cook <keescook@...omium.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Kees Cook <keescook@...omium.org>,
kernel test robot <oliver.sang@...el.com>,
Vito Caputo <vcaputo@...garu.com>,
Jann Horn <jannh@...gle.com>, Ingo Molnar <mingo@...hat.com>,
Juri Lelli <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Christian Brauner <christian.brauner@...ntu.com>,
Anand K Mistry <amistry@...gle.com>,
"Kenta.Tada@...y.com" <Kenta.Tada@...y.com>,
Alexey Gladkov <legion@...nel.org>,
Michael Weiß <michael.weiss@...ec.fraunhofer.de>,
Michal Hocko <mhocko@...e.com>, Helge Deller <deller@....de>,
Qi Zheng <zhengqi.arch@...edance.com>,
"Tobin C. Harding" <me@...in.cc>,
Tycho Andersen <tycho@...ho.pizza>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
Mark Rutland <mark.rutland@....com>,
Jens Axboe <axboe@...nel.dk>,
Stefan Metzmacher <metze@...ba.org>,
Lai Jiangshan <laijs@...ux.alibaba.com>,
Andy Lutomirski <luto@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Ohhoon Kwon <ohoono.kwon@...sung.com>,
Kalesh Singh <kaleshsingh@...gle.com>,
YiFei Zhu <yifeifz2@...inois.edu>,
Josh Poimboeuf <jpoimboe@...hat.com>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-hardening@...r.kernel.org, x86@...nel.org
Subject: [PATCH v2 0/6] wchan: Fix ORC support and leaky fallback
Hi,
This attempts to solve the issues from the discussion here[1]. Specifically:
1) wchan leaking raw addresses since 152c432b128c (v5.12).
patch 1 fixes this with a revert.
2) wchan has been broken under ORC, seen as a failure to stack walk
resulting in _usually_ a 0 value, since ee9f8fce9964 (v4.14).
patches 2-5 fixes this with Qi Zheng's new get_wchan() and changes to
the /proc code to use the new helper suggested by Peter to do the stack
walk only if the process can be kept blocked:
https://lore.kernel.org/lkml/20210929194026.GA4323@worktop.programming.kicks-ass.net/
Peter, can you take this via -tip?
Thanks!
-Kees
[1] https://lore.kernel.org/lkml/20210924054647.v6x6risoa4jhuu6s@shells.gnugeneration.com/
v1: https://lore.kernel.org/lkml/20210924062006.231699-3-keescook@chromium.org/
Kees Cook (5):
Revert "proc/wchan: use printk format instead of lookup_symbol_name()"
sched: Add wrapper for get_wchan() to keep task blocked
proc: Use task_is_running() for wchan in /proc/$pid/stat
proc: Only report /proc/$pid/wchan when process is blocked
leaking_addresses: Always print a trailing newline
Qi Zheng (1):
x86: Fix get_wchan() to support the ORC unwinder
arch/x86/kernel/process.c | 51 +++---------------------------------
fs/proc/array.c | 7 ++---
fs/proc/base.c | 20 ++++++++------
include/linux/sched.h | 1 +
kernel/sched/core.c | 16 +++++++++++
scripts/leaking_addresses.pl | 3 ++-
6 files changed, 36 insertions(+), 62 deletions(-)
--
2.30.2
Powered by blists - more mailing lists