aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/scripts/generate_rust_analyzer.py
diff options
context:
space:
mode:
authorChristian Brauner <brauner@kernel.org>2025-01-04 09:56:42 +0100
committerChristian Brauner <brauner@kernel.org>2025-01-04 10:12:19 +0100
commit6a4ef7a2ff4dfdb7b345b13bd74fc68fe351bb45 (patch)
tree785e008a7ebbfceed344f84b34bfdef5d0810d96 /scripts/generate_rust_analyzer.py
parentpipe_read: don't wake up the writer if the pipe is still full (diff)
parentselftests: coredump: Add stackdump test (diff)
downloadwireguard-linux-6a4ef7a2ff4dfdb7b345b13bd74fc68fe351bb45.tar.xz
wireguard-linux-6a4ef7a2ff4dfdb7b345b13bd74fc68fe351bb45.zip
Merge patch series "fix reading ESP during coredump"
Nam Cao <namcao@linutronix.de> says: In /proc/PID/stat, there is the kstkesp field which is the stack pointer of a thread. While the thread is active, this field reads zero. But during a coredump, it should have a valid value. However, at the moment, kstkesp is zero even during coredump. The first commit fixes this problem, and the second commit adds a selftest to detect if this problem appears again in the future. * patches from https://lore.kernel.org/r/cover.1735805772.git.namcao@linutronix.de: selftests: coredump: Add stackdump test fs/proc: do_task_stat: Fix ESP not readable during coredump Link: https://lore.kernel.org/r/cover.1735805772.git.namcao@linutronix.de Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions