From: Andrew Morton <akpm@linux-foundation.org>
To: Oxana Kharitonova <oxana@cloudflare.com>
Cc: brauner@kernel.org, bsegall@google.com, dietmar.eggemann@arm.com,
jack@suse.cz, juri.lelli@redhat.com, mgorman@suse.de,
mingo@redhat.com, peterz@infradead.org, rostedt@goodmis.org,
vincent.guittot@linaro.org, viro@zeniv.linux.org.uk,
vschneid@redhat.com, kernel-team@cloudflare.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH resend] hung_task: add task->flags, blocked by coredump to log
Date: Fri, 10 Jan 2025 19:54:45 -0800 [thread overview]
Message-ID: <20250110195445.586a1682302e66788e83e83e@linux-foundation.org> (raw)
In-Reply-To: <20250110160328.64947-1-oxana@cloudflare.com>
On Fri, 10 Jan 2025 16:03:28 +0000 Oxana Kharitonova <oxana@cloudflare.com> wrote:
> Resending this patch as I haven't received feedback on my initial
> submission https://lore.kernel.org/all/20241204182953.10854-1-oxana@cloudflare.com/
>
> For the processes which are terminated abnormally the kernel can provide
> a coredump if enabled. When the coredump is performed, the process and
> all its threads are put into the D state
> (TASK_UNINTERRUPTIBLE | TASK_FREEZABLE).
>
> On the other hand, we have kernel thread khungtaskd which monitors the
> processes in the D state. If the task stuck in the D state more than
> kernel.hung_task_timeout_secs, the hung_task alert appears in the kernel
> log.
>
> The higher memory usage of a process, the longer it takes to create
> coredump, the longer tasks are in the D state. We have hung_task alerts
> for the processes with memory usage above 10Gb. Although, our
> kernel.hung_task_timeout_secs is 10 sec when the default is 120 sec.
>
> Adding additional information to the log that the task is blocked by
> coredump will help with monitoring. Another approach might be to
> completely filter out alerts for such tasks, but in that case we would
> lose transparency about what is putting pressure on some system
> resources, e.g. we saw an increase in I/O when coredump occurs due its
> writing to disk.
>
> Additionally, it would be helpful to have task_struct->flags in the log
> from the function sched_show_task(). Currently it prints
> task_struct->thread_info->flags, this seems misleading as the line
> starts with "task:xxxx".
>
I added the below fix.
From: Andrew Morton <akpm@linux-foundation.org>
Subject: hung_task-add-task-flags-blocked-by-coredump-to-log-fix
Date: Fri Jan 10 07:51:53 PM PST 2025
fix printk control string
In file included from ./include/asm-generic/bug.h:22,
from ./arch/x86/include/asm/bug.h:99,
from ./include/linux/bug.h:5,
from ./arch/x86/include/asm/paravirt.h:19,
from ./arch/x86/include/asm/irqflags.h:80,
from ./include/linux/irqflags.h:18,
from ./include/linux/spinlock.h:59,
from ./include/linux/wait.h:9,
from ./include/linux/wait_bit.h:8,
from ./include/linux/fs.h:6,
from ./include/linux/highmem.h:5,
from kernel/sched/core.c:10:
kernel/sched/core.c: In function 'sched_show_task':
./include/linux/kern_levels.h:5:25: error: format '%lx' expects argument of type 'long unsigned int', but argument 6 has type 'unsigned int' [-Werror=format=]
5 | #define KERN_SOH "\001" /* ASCII Start Of Header */
| ^~~~~~
./include/linux/printk.h:473:25: note: in definition of macro 'printk_index_wrap'
473 | _p_func(_fmt, ##__VA_ARGS__); \
| ^~~~
./include/linux/printk.h:586:9: note: in expansion of macro 'printk'
586 | printk(KERN_CONT fmt, ##__VA_ARGS__)
| ^~~~~~
./include/linux/kern_levels.h:24:25: note: in expansion of macro 'KERN_SOH'
24 | #define KERN_CONT KERN_SOH "c"
| ^~~~~~~~
./include/linux/printk.h:586:16: note: in expansion of macro 'KERN_CONT'
586 | printk(KERN_CONT fmt, ##__VA_ARGS__)
| ^~~~~~~~~
kernel/sched/core.c:7704:9: note: in expansion of macro 'pr_cont'
7704 | pr_cont(" stack:%-5lu pid:%-5d tgid:%-5d ppid:%-6d task_flags:0x%08lx flags:0x%08lx\n",
| ^~~~~~~
cc1: all warnings being treated as errors
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Ben Segall <bsegall@google.com>
Cc: Christian Brauner <brauner@kernel.org>
Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Jan Kara <jack@suse.cz>
Cc: Juri Lelli <juri.lelli@redhat.com>
Cc: Mel Gorman <mgorman@suse.de>
Cc: Oxana Kharitonova <oxana@cloudflare.com>
Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Valentin Schneider <vschneid@redhat.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/sched/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/kernel/sched/core.c~hung_task-add-task-flags-blocked-by-coredump-to-log-fix
+++ a/kernel/sched/core.c
@@ -7701,7 +7701,7 @@ void sched_show_task(struct task_struct
if (pid_alive(p))
ppid = task_pid_nr(rcu_dereference(p->real_parent));
rcu_read_unlock();
- pr_cont(" stack:%-5lu pid:%-5d tgid:%-5d ppid:%-6d task_flags:0x%08lx flags:0x%08lx\n",
+ pr_cont(" stack:%-5lu pid:%-5d tgid:%-5d ppid:%-6d task_flags:0x%04x flags:0x%08lx\n",
free, task_pid_nr(p), task_tgid_nr(p),
ppid, p->flags, read_task_thread_flags(p));
_
next prev parent reply other threads:[~2025-01-11 3:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 16:03 [PATCH resend] hung_task: add task->flags, blocked by coredump to log Oxana Kharitonova
2025-01-11 3:54 ` Andrew Morton [this message]
2025-01-13 11:57 ` Oxana Kharitonova
2025-01-11 10:10 ` kernel test robot
2025-01-11 10:55 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250110195445.586a1682302e66788e83e83e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jack@suse.cz \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=oxana@cloudflare.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=viro@zeniv.linux.org.uk \
--cc=vschneid@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.