Re: [PATCH v6 6/6] fs/resctrl: Disallow monitor group move when the RMID index changes
From: Ben Horgan
Date: Thu Nov 19 2026 - 11:57:38 EST
Hi Jinjie,
On 19/11/2026 09:48, Jinjie Ruan wrote:
> From: Peter Newman <peternewman@xxxxxxxxxx>
>
> A MON group can be moved into the mon_groups directory of another
> CTRL_MON group to move its tasks to that group's allocation while
> keeping their monitoring data. Where the RMID is only meaningful
> together with the CLOSID, as on arm64 MPAM where the RMID is a PMG that
> extends the PARTID, the move changes the RMID index of the group. The
> move succeeds, but:
>
> - The group's monitoring data is reset. Its counters are identified by
> the CLOSID and RMID together, so after the move the group reads the
> counters of the new CLOSID instead of the ones its tasks used.
>
> - The group uses an RMID index that was never allocated to it. When
> the group is removed, free_rmid() puts an RMID index of the new CLOSID
> into limbo without checking that the group owns it. If another group
> of that CLOSID holds the index, the limbo handler tests and frees an
> RMID that is still in use, while the RMID index allocated to the
> moved group is never freed. If no other group holds it, the index is
> in use while it is considered free for allocation.
>
> - The tasks are not moved. mongrp_reparent() sets the new parent and
> CLOSID of the group before rdt_move_group_tasks() looks for the tasks
> to update, and the search then matches on the new CLOSID, which none
> of the tasks carries yet. The tasks keep the old CLOSID and the old
> CTRL_MON group's allocation, and the group does not count them.
>
> Fixing the task move does not make the move work. The RMID index is the
> hardware ID the counters count for, so a group whose CLOSID changes
> cannot keep its monitoring data, and it would need a new RMID index
> allocated for the new CLOSID, which fails when every RMID index of that
> CLOSID is in use. The documentation promises that a move keeps the
> monitoring data, so the move cannot be supported, as decided in the
> thread at the Link tag.
>
> Reject the move with -EOPNOTSUPP when it changes the RMID index of the
> group, and document that a move is not allowed when the monitoring data
> or assigned tasks would be impacted. Leave the move allowed where the
> RMID does not depend on the CLOSID, such as on x86, and leave renaming
> within the same CTRL_MON group allowed everywhere; neither changes the
> RMID index.
>
> Fixes: 3e9b35823aab ("arm_mpam: resctrl: Add rmid index helpers")
> Signed-off-by: Peter Newman <peternewman@xxxxxxxxxx>
> Signed-off-by: Jinjie Ruan <ruanjinjie@xxxxxxxxxx>
> Reviewed-by: Reinette Chatre <reinette.chatre@xxxxxxxxx>
> Cc: <stable@xxxxxxxxxxxxxxx>
> Link: https://lore.kernel.org/lkml/3a637631-c8ec-4e26-a03c-5ac80d16fab3@xxxxxxx/
Looks good to me.
Reviewed-by: Ben Horgan <ben.horgan@xxxxxxx>
> ---
> v6:
> - Describe the RMID index that is used while it is considered free, and
> keep the last paragraph imperative (Reinette).
> v5:
> - Retitle as the RMID index changes, not the RMID, and a rename within
> the same CTRL_MON group is still allowed.
> - Describe the RMID index that is freed without having been allocated,
> and why the move cannot be fixed instead of being rejected.
> - Drop the parent and resctrl_arch_mon_capable() checks, which the RMID
> index comparison and the MON group check already cover.
> - Use the resctrl.rst terms in the last_cmd_status message.
> - Drop the stable version range and the Link tags the changelog did not
> refer to, and link the decision to reject the move instead.
> - Link to v2: https://lore.kernel.org/all/20261105123524.2282090-1-ruanjinjie@xxxxxxxxxx/
> v2:
> - Drop the Suggested-by tag.
> - Describe the systems by whether the RMID depends on the CLOSID rather
> than by MPAM, in both the changelog and resctrl.rst.
> - Explain that moving a monitor group is already broken on these systems
> because the tasks are not moved, so no existing user relies on it.
> - v1: https://lore.kernel.org/all/20261104101913.586595-1-ruanjinjie@xxxxxxxxxx/
> ---
> Documentation/filesystems/resctrl.rst | 8 ++++----
> fs/resctrl/rdtgroup.c | 13 +++++++++++++
> 2 files changed, 17 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/filesystems/resctrl.rst b/Documentation/filesystems/resctrl.rst
> index b52795e03303..fecb2cd2b343 100644
> --- a/Documentation/filesystems/resctrl.rst
> +++ b/Documentation/filesystems/resctrl.rst
> @@ -551,10 +551,10 @@ will automatically remove all MON groups below it.
>
> Moving MON group directories to a new parent CTRL_MON group is supported
> for the purpose of changing the resource allocations of a MON group
> -without impacting its monitoring data or assigned tasks. This operation
> -is not allowed for MON groups which monitor CPUs. No other move
> -operation is currently allowed other than simply renaming a CTRL_MON or
> -MON group.
> +without impacting its monitoring data or assigned tasks. This operation is
> +not allowed for MON groups which monitor CPUs, or when the monitoring data
> +or assigned tasks would be impacted. No other move operation is currently
> +allowed other than simply renaming a CTRL_MON or MON group.
>
> All groups contain the following files:
>
> diff --git a/fs/resctrl/rdtgroup.c b/fs/resctrl/rdtgroup.c
> index c7c4f618208d..e16ae5799e0b 100644
> --- a/fs/resctrl/rdtgroup.c
> +++ b/fs/resctrl/rdtgroup.c
> @@ -4403,6 +4403,19 @@ static int rdtgroup_rename(struct kernfs_node *kn,
> goto out;
> }
>
> + /*
> + * Moving the group to another CTRL_MON group changes its CLOSID.
> + * Where the RMID is only meaningful together with the CLOSID, this
> + * changes the RMID index and the monitor state cannot follow the
> + * move. A rename within the same CTRL_MON group keeps the index.
> + */
> + if (resctrl_arch_rmid_idx_encode(rdtgrp->closid, rdtgrp->mon.rmid) !=
> + resctrl_arch_rmid_idx_encode(new_prdtgrp->closid, rdtgrp->mon.rmid)) {
> + rdt_last_cmd_puts("Moving a MON group to a new CTRL_MON group is not supported\n");
> + ret = -EOPNOTSUPP;
> + goto out;
> + }
> +
> /*
> * If the MON group is monitoring CPUs, the CPUs must be assigned to the
> * current parent CTRL_MON group and therefore cannot be assigned to