From: Greg KH <gregkh@linuxfoundation.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: stable@vger.kernel.org, manish1@arista.com
Subject: Re: Please backport b8e753128ed074 (exit: Sleep at TASK_IDLE when waiting for application core dump) to < 6.12
Date: Wed, 13 May 2026 17:32:10 +0200 [thread overview]
Message-ID: <2026051303-derby-oversweet-263d@gregkh> (raw)
In-Reply-To: <35e9c59e-6e54-4683-9751-175d425fbc37@molgen.mpg.de>
On Wed, May 13, 2026 at 03:24:28PM +0200, Paul Menzel wrote:
> Dear Linux folks,
>
>
> I am forwarding a backport request from SONiC Linux kernel [1]. It’d be
> great if you could apply commit b8e753128ed074fcb48e9ceded940752f6b1c19f [2]
> to Linux 6.1 and older.
>
> > On Linux 6.1, coredump_task_exit() parks sibling threads in
> > TASK_UNINTERRUPTIBLE|TASK_FREEZABLE while one thread of the group
> > writes the core file. Under sustained memory pressure the dump can
> > take longer than kernel.hung_task_timeout_secs, at which point
> > khungtaskd flags the parked siblings and (with hung_task_panic=1)
> > panics the box.
> >
> > Backport mainline v6.12 commit b8e753128ed0 ("exit: Sleep at
> > TASK_IDLE when waiting for application core dump") which switches
> > that wait to TASK_IDLE|TASK_FREEZABLE so the watchdog skips it.
>
>
> Kind regards,
>
> Paul
>
>
> [1]: https://github.com/sonic-net/sonic-linux-kernel/pull/575/
> [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b8e753128ed074fcb48e9ceded940752f6b1c19f
>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2026-05-13 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 13:24 Please backport b8e753128ed074 (exit: Sleep at TASK_IDLE when waiting for application core dump) to < 6.12 Paul Menzel
2026-05-13 15:32 ` Greg KH [this message]
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=2026051303-derby-oversweet-263d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=manish1@arista.com \
--cc=pmenzel@molgen.mpg.de \
--cc=stable@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox