Re: [PATCH 11/27] block: Protect against concurrent isolated cpuset change

From: Christoph Hellwig
Date: Mon Jun 23 2025 - 01:47:09 EST

Next message: Mukesh Ojha: "Re: [PATCH] pinmux: fix race causing mux_owner NULL with active mux_usecount"
Previous message: Vasanthakumar Thiagarajan: "Re: [PATCH ath-next 0/2] wifi: ath12k: install pairwise key first"
In reply to: Bart Van Assche: "Re: [PATCH 11/27] block: Protect against concurrent isolated cpuset change"
Next in thread: Frederic Weisbecker: "[PATCH 16/27] sched/isolation: Flush memcg workqueues on cpuset isolated partition change"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri, Jun 20, 2025 at 05:22:52PM +0200, Frederic Weisbecker wrote:
> + * running block kworker on isolated CPUs.
> + * FIXME: cpuset should propagate further changes to isolated CPUs
> + * here.

I have no idea what this comments means. Can you explain it, or help
fixing it? Or at least send the entire series to all affected
subsystems as there's no way to review it without the context.

If nothing changes please at leat avoid the overly long line.

Next message: Mukesh Ojha: "Re: [PATCH] pinmux: fix race causing mux_owner NULL with active mux_usecount"
Previous message: Vasanthakumar Thiagarajan: "Re: [PATCH ath-next 0/2] wifi: ath12k: install pairwise key first"
In reply to: Bart Van Assche: "Re: [PATCH 11/27] block: Protect against concurrent isolated cpuset change"
Next in thread: Frederic Weisbecker: "[PATCH 16/27] sched/isolation: Flush memcg workqueues on cpuset isolated partition change"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]