From: Adrian Hunter <adrian.hunter@intel.com>
To: <alexandre.belloni@bootlin.com>, <Frank.Li@nxp.com>
Cc: <david.nystrom@est.tech>, <linux-i3c@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 2/8] i3c: master: Serialize i3c_set_hotjoin() with the maintenance lock
Date: Fri, 5 Jun 2026 18:04:00 +0300 [thread overview]
Message-ID: <31683eb0-7514-4bf6-9c57-803ed58be4da@intel.com> (raw)
In-Reply-To: <20260518115520.98335-3-adrian.hunter@intel.com>
On 18/05/2026 14:55, Adrian Hunter wrote:
> i3c_set_hotjoin() dispatches the controller's enable_hotjoin() or
> disable_hotjoin() op and updates master->hotjoin under
> i3c_bus_normaluse_lock(). That lock is a read-side acquisition of
> bus->lock (down_read()), so it does not exclude concurrent callers.
>
> The hotjoin sysfs attribute can be opened multiple times, and writes
> through different opens are not serialized. Two concurrent writers
> to "hotjoin" can therefore race in i3c_set_hotjoin(), with the
> controller op and the master->hotjoin store from one call interleaving
> with the other. The hardware enable/disable state and the value reported
> by hotjoin_show() can end up out of sync.
>
> Take i3c_bus_maintenance_lock() instead. Toggling Hot Join enable
> changes bus state and is conceptually a maintenance operation, so the
> write-side acquisition of bus->lock is the appropriate lock and
> serializes concurrent callers against each other and against other
> maintenance operations.
>
> Fixes: 317bacf960a48 ("i3c: master: add enable(disable) hot join in sys entry")
> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
Any comments on this patch?
> ---
>
>
> Changes in V2:
>
> Add Fixes tag
>
>
> drivers/i3c/master.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c
> index ab11e2d79aab..38ffc8713167 100644
> --- a/drivers/i3c/master.c
> +++ b/drivers/i3c/master.c
> @@ -649,7 +649,7 @@ static int i3c_set_hotjoin(struct i3c_master_controller *master, bool enable)
> return ret;
> }
>
> - i3c_bus_normaluse_lock(&master->bus);
> + i3c_bus_maintenance_lock(&master->bus);
>
> if (enable)
> ret = master->ops->enable_hotjoin(master);
> @@ -659,7 +659,7 @@ static int i3c_set_hotjoin(struct i3c_master_controller *master, bool enable)
> if (!ret)
> master->hotjoin = enable;
>
> - i3c_bus_normaluse_unlock(&master->bus);
> + i3c_bus_maintenance_unlock(&master->bus);
>
> if ((enable && ret) || (!enable && !ret) || master->rpm_ibi_allowed)
> i3c_master_rpm_put(master);
next prev parent reply other threads:[~2026-06-05 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 11:55 [PATCH V2 0/8] i3c: Hot-Join improvements and MIPI HCI Hot-Join support Adrian Hunter
2026-05-18 11:55 ` [PATCH V2 1/8] i3c: master: Make hot-join workqueue freezable to block hot-join during suspend Adrian Hunter
2026-05-18 11:55 ` [PATCH V2 2/8] i3c: master: Serialize i3c_set_hotjoin() with the maintenance lock Adrian Hunter
2026-06-05 15:04 ` Adrian Hunter [this message]
2026-06-05 16:19 ` Frank Li
2026-05-18 11:55 ` [PATCH V2 3/8] i3c: master: Consolidate Hot-Join DAA work in the core Adrian Hunter
2026-05-18 11:55 ` [PATCH V2 4/8] i3c: master: Ensure Hot-Join operations are stopped on shutdown Adrian Hunter
2026-05-18 11:55 ` [PATCH V2 5/8] i3c: dw: Drop redundant Hot-Join cancel_work_sync() in shutdown Adrian Hunter
2026-05-18 11:55 ` [PATCH V2 6/8] i3c: master: Defer new-device registration out of DAA caller context Adrian Hunter
2026-06-05 16:23 ` Frank Li
2026-05-18 11:55 ` [PATCH V2 7/8] i3c: master: Export i3c_master_enec_disec_locked() Adrian Hunter
2026-05-18 11:55 ` [PATCH V2 8/8] i3c: mipi-i3c-hci: Add Hot-Join support Adrian Hunter
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=31683eb0-7514-4bf6-9c57-803ed58be4da@intel.com \
--to=adrian.hunter@intel.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=david.nystrom@est.tech \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox