All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,konishi.ryusuke@gmail.com,haokexin@gmail.com,akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] nilfs2-add-missing-set_freezable-for-freezable-kthread.patch removed from -mm tree
Date: Fri, 29 Dec 2023 12:23:23 -0800	[thread overview]
Message-ID: <20231229202323.8FC22C433C8@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: nilfs2: add missing set_freezable() for freezable kthread
has been removed from the -mm tree.  Its filename was
     nilfs2-add-missing-set_freezable-for-freezable-kthread.patch

This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Kevin Hao <haokexin@gmail.com>
Subject: nilfs2: add missing set_freezable() for freezable kthread
Date: Tue, 19 Dec 2023 18:09:18 +0900

The kernel thread function nilfs_segctor_thread() invokes the
try_to_freeze() in its loop.  But all the kernel threads are non-freezable
by default.  So if we want to make a kernel thread to be freezable, we
have to invoke set_freezable() explicitly.

Link: https://lkml.kernel.org/r/20231219090918.2329-1-konishi.ryusuke@gmail.com
Signed-off-by: Kevin Hao <haokexin@gmail.com>
Signed-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 fs/nilfs2/segment.c |    1 +
 1 file changed, 1 insertion(+)

--- a/fs/nilfs2/segment.c~nilfs2-add-missing-set_freezable-for-freezable-kthread
+++ a/fs/nilfs2/segment.c
@@ -2588,6 +2588,7 @@ static int nilfs_segctor_thread(void *ar
 		   "segctord starting. Construction interval = %lu seconds, CP frequency < %lu seconds",
 		   sci->sc_interval / HZ, sci->sc_mjcp_freq / HZ);
 
+	set_freezable();
 	spin_lock(&sci->sc_state_lock);
  loop:
 	for (;;) {
_

Patches currently in -mm which might be from haokexin@gmail.com are



                 reply	other threads:[~2023-12-29 20:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20231229202323.8FC22C433C8@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=haokexin@gmail.com \
    --cc=konishi.ryusuke@gmail.com \
    --cc=mm-commits@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 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.