[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1559591648.29720.5.camel@pengutronix.de>
Date: Mon, 03 Jun 2019 21:54:08 +0200
From: Jan Lübbe <jlu@...gutronix.de>
To: John Ogness <john.ogness@...utronix.de>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Alexey Dobriyan <adobriyan@...il.com>,
Andy Lutomirski <luto@...nel.org>, kernel@...gutronix.de,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCHv3] fs/proc: allow reporting eip/esp for all coredumping
threads
On Thu, 2019-05-30 at 02:58 +0200, John Ogness wrote:
> Commit 0a1eb2d474ed ("fs/proc: Stop reporting eip and esp in
> /proc/PID/stat") stopped reporting eip/esp and commit fd7d56270b52
> ("fs/proc: Report eip/esp in /prod/PID/stat for coredumping")
> reintroduced the feature to fix a regression with userspace core dump
> handlers (such as minicoredumper).
>
> Because PF_DUMPCORE is only set for the primary thread, this didn't fix
> the original problem for secondary threads. Allow reporting the eip/esp
> for all threads by checking for PF_EXITING as well. This is set for all
> the other threads when they are killed. coredump_wait() waits for all
> the tasks to become inactive before proceeding to invoke a core dumper.
>
> Fixes: fd7d56270b526ca3 ("fs/proc: Report eip/esp in /prod/PID/stat for coredumping")
> Reported-by: Jan Luebbe <jlu@...gutronix.de>
> Signed-off-by: John Ogness <john.ogness@...utronix.de>
Tested-by: Jan Luebbe <jlu@...gutronix.de>
I've tested your patch and can confirm that eip/esp is accessible for
all threads again.
Thanks,
Jan
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Powered by blists - more mailing lists