From: Ben Horgan <ben.horgan@arm.com>
To: Ping Li <leeonion.muyu@gmail.com>, james.morse@arm.com
Cc: andre.przywara@arm.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, reinette.chatre@intel.com,
fenghuay@nvidia.com
Subject: Re: [PATCH] arm_mpam: Release the mon_sel lock on mpam_save_mbwu_state() errors
Date: Wed, 21 Oct 2026 10:01:36 +0100 [thread overview]
Message-ID: <f73ab1cf-490e-4e81-8307-92f5eaae12c7@arm.com> (raw)
In-Reply-To: <20261020114807.3915705-1-leeonion.muyu@gmail.com>
Hi Ping,
On 20/10/2026 12:48, Ping Li wrote:
> mpam_save_mbwu_state() takes the mon_sel lock at the top of each loop
> iteration, but the four error paths that return after failed
> MPAMF_MON_SEL register accesses do so without releasing it.
>
> Take the lock with the conditional mon_sel_lock guard class instead,
> so all exit paths release it.
>
> Fixes: a3a94c13c442 ("arm_mpam: propagate MSC access errors for state saving function")
> Signed-off-by: Ping Li <leeonion.muyu@gmail.com>
Thanks for this. Looks like this was a result of the conflict between the MPAM-Fb series and my
minor fixes series.
Reviewed-by: Ben Horgan <ben.horgan@arm.com>
Cheers,
Ben
> ---
> drivers/resctrl/mpam_devices.c | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/resctrl/mpam_devices.c b/drivers/resctrl/mpam_devices.c
> index 48adc49b833c..c067b6d57d71 100644
> --- a/drivers/resctrl/mpam_devices.c
> +++ b/drivers/resctrl/mpam_devices.c
> @@ -2037,8 +2037,10 @@ static int mpam_save_mbwu_state(void *arg)
> struct mpam_class *class = ris->vmsc->comp->class;
>
> for (i = 0; i < ris->props.num_mbwu_mon; i++) {
> - if (WARN_ON_ONCE(!mpam_mon_sel_lock(msc)))
> - return -EIO;
> + ACQUIRE(mon_sel_lock, guard)(msc);
> + ret = ACQUIRE_ERR(mon_sel_lock, &guard);
> + if (ret)
> + return ret;
>
> mbwu_state = &ris->mbwu_state[i];
> cfg = &mbwu_state->cfg;
> @@ -2061,10 +2063,8 @@ static int mpam_save_mbwu_state(void *arg)
> cfg->partid = FIELD_GET(MSMON_CFG_x_FLT_PARTID, cur_flt);
> mbwu_state->enabled = FIELD_GET(MSMON_CFG_x_CTL_EN, cur_ctl);
>
> - if (!mbwu_state->enabled) {
> - mpam_mon_sel_unlock(msc);
> + if (!mbwu_state->enabled)
> continue;
> - }
>
> val = 0;
> mbwu_arg = (struct mon_read) {
> @@ -2088,8 +2088,6 @@ static int mpam_save_mbwu_state(void *arg)
> ret = mpam_write_monsel_reg(msc, CFG_MBWU_CTL, 0);
> if (ret)
> return ret;
> -
> - mpam_mon_sel_unlock(msc);
> }
>
> return 0;
>
> base-commit: 8ea457f746d915d55f78b43d33b1cd618f3d93ad
next prev parent reply other threads:[~2026-10-21 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 11:48 Ping Li
2026-10-21 9:01 ` Ben Horgan [this message]
[not found] <20261020114807.3915705-1-leeonion.muyu@gmail.com_quarantine>
2026-10-21 9:26 ` Andre Przywara
2026-10-21 10:45 ` Ben Horgan
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=f73ab1cf-490e-4e81-8307-92f5eaae12c7@arm.com \
--to=ben.horgan@arm.com \
--cc=andre.przywara@arm.com \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=leeonion.muyu@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
/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®