mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
	oleg@redhat.com, axboe@kernel.dk, brauner@kernel.org,
	akpm@linux-foundation.org, willy@infradead.org, clm@fb.com,
	riel@surriel.com
Subject: [GIT PULL] exit/core-dump non-urgent sleep for v6.12
Date: Sat, 14 Sep 2024 01:16:38 -0700	[thread overview]
Message-ID: <bb2c5f74-2f89-4bb5-9d49-3061c218dde9@paulmck-laptop> (raw)

Hello, Linus,

When the merge window opens, please pull the following exit-path
application core-dump commit for v6.12:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/misc.2024.09.14a
  # HEAD: b8e753128ed074fcb48e9ceded940752f6b1c19f: exit: Sleep at TASK_IDLE when waiting for application core dump (2024-08-02 10:55:04 -0700)

No, this is not my usual part of the kernel, but it does have Oleg
Nesterov's ack.

----------------------------------------------------------------
exit: Sleep at TASK_IDLE when waiting for application core dump

This causes the coredump_task_exit() function to sleep at TASK_IDLE,
thus preventing task-blocked splats in case of large core dumps to
slow devices.

----------------------------------------------------------------
Paul E. McKenney (1):
      exit: Sleep at TASK_IDLE when waiting for application core dump

 kernel/exit.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

             reply	other threads:[~2024-09-14  8:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-14  8:16 Paul E. McKenney [this message]
2024-09-18  8:10 ` pr-tracker-bot

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=bb2c5f74-2f89-4bb5-9d49-3061c218dde9@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=clm@fb.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=riel@surriel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.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

all inboxes | Powered by JetHome®