Linux kernel -stable discussions
 help / color / mirror / Atom feed
* [PATCHv3] fs/proc: allow reporting eip/esp for all coredumping threads
       [not found]       ` <87y32p7i7a.fsf@linutronix.de>
@ 2019-05-30  0:58         ` John Ogness
  2019-05-30  1:14           ` Andrew Morton
  2019-06-03 19:54           ` Jan Lübbe
  0 siblings, 2 replies; 3+ messages in thread
From: John Ogness @ 2019-05-30  0:58 UTC (permalink / raw)
  To: Jan Luebbe
  Cc: Andrew Morton, Alexey Dobriyan, Andy Lutomirski, kernel,
	linux-kernel, linux-fsdevel, stable

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@pengutronix.de>
Signed-off-by: John Ogness <john.ogness@linutronix.de>
---
 This is a rework of Jan's v1 patch that allows accessing eip/esp of all
 the threads without risk of the task still executing on a CPU.

 The code chagnes are the same as v2. With v3 I included a "Fixes" tag,
 fixed a typo in the commit message, and Cc'd stable.

 fs/proc/array.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/proc/array.c b/fs/proc/array.c
index 2edbb657f859..55180501b915 100644
--- a/fs/proc/array.c
+++ b/fs/proc/array.c
@@ -462,7 +462,7 @@ static int do_task_stat(struct seq_file *m, struct pid_namespace *ns,
 		 * a program is not able to use ptrace(2) in that case. It is
 		 * safe because the task has stopped executing permanently.
 		 */
-		if (permitted && (task->flags & PF_DUMPCORE)) {
+		if (permitted && (task->flags & (PF_EXITING|PF_DUMPCORE))) {
 			if (try_get_task_stack(task)) {
 				eip = KSTK_EIP(task);
 				esp = KSTK_ESP(task);
-- 
2.11.0

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCHv3] fs/proc: allow reporting eip/esp for all coredumping threads
  2019-05-30  0:58         ` [PATCHv3] fs/proc: allow reporting eip/esp for all coredumping threads John Ogness
@ 2019-05-30  1:14           ` Andrew Morton
  2019-06-03 19:54           ` Jan Lübbe
  1 sibling, 0 replies; 3+ messages in thread
From: Andrew Morton @ 2019-05-30  1:14 UTC (permalink / raw)
  To: John Ogness
  Cc: Jan Luebbe, Alexey Dobriyan, Andy Lutomirski, kernel,
	linux-kernel, linux-fsdevel, stable

(ooh, Greg, let me do it!)

On Thu, 30 May 2019 02:58:59 +0200 John Ogness <john.ogness@linutronix.de> 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@pengutronix.de>
> Signed-off-by: John Ogness <john.ogness@linutronix.de>
> ---
>  This is a rework of Jan's v1 patch that allows accessing eip/esp of all
>  the threads without risk of the task still executing on a CPU.
> 
>  The code chagnes are the same as v2. With v3 I included a "Fixes" tag,
>  fixed a typo in the commit message, and Cc'd stable.

No, the way to Cc stable is to add

Cc: <stable@vger.kernel.org> to the changelog metadata.

I've made these changes to my copy of this patch, thanks.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCHv3] fs/proc: allow reporting eip/esp for all coredumping threads
  2019-05-30  0:58         ` [PATCHv3] fs/proc: allow reporting eip/esp for all coredumping threads John Ogness
  2019-05-30  1:14           ` Andrew Morton
@ 2019-06-03 19:54           ` Jan Lübbe
  1 sibling, 0 replies; 3+ messages in thread
From: Jan Lübbe @ 2019-06-03 19:54 UTC (permalink / raw)
  To: John Ogness
  Cc: Andrew Morton, Alexey Dobriyan, Andy Lutomirski, kernel,
	linux-kernel, linux-fsdevel, stable

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@pengutronix.de>
> Signed-off-by: John Ogness <john.ogness@linutronix.de>

Tested-by: Jan Luebbe <jlu@pengutronix.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 |

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-06-03 19:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20190522161614.628-1-jlu@pengutronix.de>
     [not found] ` <875zpzif8v.fsf@linutronix.de>
     [not found]   ` <20190525143220.e771b7915d17f22dad1438fa@linux-foundation.org>
     [not found]     ` <87d0k5f1g7.fsf@linutronix.de>
     [not found]       ` <87y32p7i7a.fsf@linutronix.de>
2019-05-30  0:58         ` [PATCHv3] fs/proc: allow reporting eip/esp for all coredumping threads John Ogness
2019-05-30  1:14           ` Andrew Morton
2019-06-03 19:54           ` Jan Lübbe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox