Linux filesystem development
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	fuse-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] fuse: permit freezing while waiting for request answer
Date: Fri, 21 Aug 2026 13:03:14 +0200	[thread overview]
Message-ID: <20260821110314.GK788244@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260821083000.GF687043@noisy.programming.kicks-ass.net>

On Fri, Aug 21, 2026 at 10:30:00AM +0200, Peter Zijlstra wrote:

> Another approach might be to have each task have a list of tasks that
> needs to be done later, and have this relation be counted in the
> destination task.
> 
> Then, on freeze, create a list of all tasks and start iteration, for
> each task that has a non-zero count of prior tasks, move it to the tail.
> This relies on freeze points being a location where a task has no
> relations. Such that when a task is frozen, it has no dependencies.
> 
> Then, again assuming it was a non-cyclic graph, it will always finish
> the freeze in an order that resolves the dependencies.
> 
> This might be a little more tricky to implement, but should be doable.
> 
> In both scenarios the tracking of the actual dependencies is of course
> going to be key.
> 
> One way would be for each file op to be wrapped like 'link-$op-unlink'
> such that the client (the task doing the file op) gets linked to the
> server (the task responsible for satisfying the request) before it can
> block, and unlinked once its done.
> 
> Link/unlink could be a simple as:
> 
> 	struct task_struct *client, *server;
> 
> link;
> 	atomic_inc(&server->freezer_count);
> 	client->freezer_link = server;
> 
> unlink:
> 
> 	atomic_dec(&client->freezer_link->freezer_count);
> 	client->freezer_link = NULL;
> 
> And the freezer should assert: !task->freezer_link, to ensure you
> cannot be frozen while still having a link out, since this would keep
> the link target's count elevated and inhibit freezer forever more.
> 
> This also deals with the server being a client of yet another fuse
> filesystem. Creating cycles in fuse mounts would already be a recipe
> for disaster today, without all this, so I'm assuming this all just
> 'works'.

Something like so; this is a very rough draft and only supports a single
dependent task -- if you need more (eg. threaded fuse server where there
isn't a convenient 1:1 relation) it needs a little more.

But I'm hoping the idea is clear.

---
diff --git a/include/linux/sched.h b/include/linux/sched.h
index 193a4a4dcc27..5c0cf42b4827 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -1670,6 +1670,12 @@ struct task_struct {
 	struct unwind_task_info		unwind_info;
 #endif
 
+#ifdef CONFIG_FREEZER
+	struct list_head		freezer_node;
+	struct task_struct		*freezer_link;
+	atomic_t			freezer_count;
+#endif
+
 	/* CPU-specific state of this task: */
 	struct thread_struct		thread;
 
@@ -1693,6 +1699,35 @@ static inline bool sched_proxy_exec(void)
 }
 #endif
 
+#ifdef CONFIG_FREEZER
+extern struct task_struct init_task;
+static inline void init_task_freezer_link(struct task_struct *p)
+{
+	list_add_tail(&p->freezer_node, &init_task.freezer_node);
+}
+static inline void init_task_freezer_unlink(struct task_struct *p)
+{
+	list_del(&p->freezer_node);
+}
+static inline void freezer_link(struct task_struct *server)
+{
+	WARN_ON_ONCE(current->freezer_link);
+	current->freezer_link = server;
+	atomic_inc(&server->freezer_count);
+}
+static inline void freezer_unlink(struct task_struct *server)
+{
+	WARN_ON_ONCE(current->freezer_link != server);
+	current->freezer_link = NULL;
+	atomic_dec(&server->freezer_count);
+}
+#else
+static inline void init_task_freezer_link(struct task_struct *p) { }
+static inline void init_task_freezer_unlink(struct task_struct *p) { }
+static inline void freezer_link(struct task_struct *server) { }
+static inline void freezer_unlink(struct task_struct *server) { }
+#endif
+
 #define TASK_REPORT_IDLE	(TASK_REPORT + 1)
 #define TASK_REPORT_MAX		(TASK_REPORT_IDLE << 1)
 
diff --git a/init/init_task.c b/init/init_task.c
index ba5c2523f7e0..643598217335 100644
--- a/init/init_task.c
+++ b/init/init_task.c
@@ -266,6 +266,9 @@ struct task_struct init_task __aligned(L1_CACHE_BYTES) = {
 #ifdef CONFIG_SCHED_MM_CID
 	.mm_cid		= { .cid = MM_CID_UNSET, },
 #endif
+#ifdef CONFIG_FREEZER
+	.freezer_node	= LIST_HEAD_INIT(init_task.freezer_node),
+#endif
 };
 EXPORT_SYMBOL(init_task);
 
diff --git a/kernel/exit.c b/kernel/exit.c
index e9f902be4ea6..22d9800656f1 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -291,6 +291,8 @@ void release_task(struct task_struct *p)
 			leader->exit_state = EXIT_DEAD;
 	}
 
+	init_task_freezer_unlink(p);
+
 	write_unlock_irq(&tasklist_lock);
 	/* @thread_pid can't go away until free_pids() below */
 	proc_flush_pid(thread_pid);
diff --git a/kernel/fork.c b/kernel/fork.c
index e645675dd727..86b4f30c9370 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -2506,6 +2506,7 @@ __latent_entropy struct task_struct *copy_process(
 		task_set_no_new_privs(p);
 
 	init_task_pid_links(p);
+	init_task_freezer_link(p);
 	if (likely(p->pid)) {
 		ptrace_init_task(p, (clone_flags & CLONE_PTRACE) || trace);
 
diff --git a/kernel/freezer.c b/kernel/freezer.c
index a76bf957fb32..46838be512f1 100644
--- a/kernel/freezer.c
+++ b/kernel/freezer.c
@@ -135,8 +135,10 @@ static int __set_task_frozen(struct task_struct *p, void *arg)
 	/*
 	 * It's dangerous to freeze with locks held; there be dragons there.
 	 */
-	if (!(state & __TASK_FREEZABLE_UNSAFE))
+	if (!(state & __TASK_FREEZABLE_UNSAFE)) {
 		WARN_ON_ONCE(debug_locks && p->lockdep_depth);
+		WARN_ON_ONCE(p->freezer_link);
+	}
 #endif
 
 	p->saved_state = p->__state;
diff --git a/kernel/power/process.c b/kernel/power/process.c
index dc0dfc349f22..454b02f00ec8 100644
--- a/kernel/power/process.c
+++ b/kernel/power/process.c
@@ -29,7 +29,7 @@ static int try_to_freeze_tasks(bool user_only)
 {
 	const char *what = user_only ? "user space processes" :
 					"remaining freezable tasks";
-	struct task_struct *g, *p;
+	struct task_struct *g, *p, *stop;
 	unsigned long end_time;
 	unsigned int todo;
 	bool wq_busy = false;
@@ -49,9 +49,52 @@ static int try_to_freeze_tasks(bool user_only)
 
 	while (true) {
 		todo = 0;
+		stop = NULL;
 		read_lock(&tasklist_lock);
-		for_each_process_thread(g, p) {
-			if (p == current || !freeze_task(p))
+		list_for_each_entry_safe(p, g, &init_task.freezer_node, freezer_node) {
+			/*
+			 * The head of the list will be the already frozen
+			 * tasks, skip those.
+			 */
+			if (p == current || frozen(p))
+				continue;
+
+			/*
+			 * If the task has dependencies; move it to the tail.
+			 * This is safe under read-tasklist_lock, because that
+			 * excludes clone/exit and is otherwise serialized by
+			 * the freezer -- you can't have multiple freezer
+			 * instances.
+			 */
+			if (atomic_read(&p->freezer_count)) {
+				/*
+				 * @stop tracks the 'first' task with
+				 * dependencies that is moved to the tail; if
+				 * we encounter it again while also having
+				 * failed to freeze previous tasks, we must
+				 * stop.
+				 */
+				if (p == stop && todo)
+					break;
+
+				if (!stop)
+					stop = p;
+
+				list_move_tail(&p->freezer_node, &init_task.freezer_node);
+				continue;
+			}
+
+			/*
+			 * The @stop task was previously observed to have
+			 * non-zero freezer_count, however all its
+			 * dependencies went away (got frozen) and it can be
+			 * frozen now. Clear it as a stop marker such that a
+			 * new marker can be picked.
+			 */
+			if (p == stop)
+				stop = NULL;
+
+			if (!freeze_task(p))
 				continue;
 
 			todo++;

  reply	other threads:[~2026-08-21 11:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260819023542.561653-1-senozhatsky@chromium.org>
2026-08-19 10:03 ` [PATCH v2] fuse: permit freezing while waiting for request answer Miklos Szeredi
2026-08-20  4:57   ` Sergey Senozhatsky
2026-08-20  8:49   ` Peter Zijlstra
2026-08-20  9:07     ` Sergey Senozhatsky
2026-08-20  9:10       ` Peter Zijlstra
2026-08-20  9:24         ` Sergey Senozhatsky
2026-08-20  9:34           ` Peter Zijlstra
2026-08-20  9:47             ` Sergey Senozhatsky
2026-08-20 10:41               ` Peter Zijlstra
2026-08-20 16:11                 ` Miklos Szeredi
2026-08-21  8:30                   ` Peter Zijlstra
2026-08-21 11:03                     ` Peter Zijlstra [this message]
2026-08-21 14:33                     ` Miklos Szeredi
2026-08-21 14:57                       ` Peter Zijlstra

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=20260821110314.GK788244@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=fuse-devel@lists.linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=rafael@kernel.org \
    --cc=senozhatsky@chromium.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