forked from fujitsu/crash-gcore
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
gcore: Fix the invalid struct size failure of pid_link on 4.19 and ne…
…wer kernel. On 4.19 and newer kernel, gcore command fails as following: =========================================================== gcore: invalid structure size: pid_link FILE: libgcore/gcore_coredump_table.c LINE: 423 FUNCTION: pid_alive() [./crash] error trace: 7f4a7a6762b8 => 7f4a7a676e0f => 53b391 => 53b316 53b316: SIZE_verify.part.31+70 53b391: SIZE_verify+49 gcore: invalid structure size: pid_link FILE: libgcore/gcore_coredump_table.c LINE: 423 FUNCTION: pid_alive() Failed. =========================================================== That is because struct pid_link is removed and struct pid array is added to struct signal_struct by commit 2c4704756cab ("pids: Move the pgrp and session pid pointers from task_struct to signal_struct"). Get the pointer of struct pid from task_struct->thread_pid or signal_struct->pids[] to fix the failure. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1722726 Signed-off-by: Masayoshi Mizuma <[email protected]>
- Loading branch information
1 parent
a03d5a5
commit 0370012
Showing
3 changed files
with
46 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters