From: Dave Jiang <dave.jiang@intel.com>
To: jdmason@kudzu.us, allenbh@gmail.com, ntb@lists.linux.dev,
linux-kernel@vger.kernel.org, fuyuanli0722@gmail.com
Subject: Re: [PATCH v2] ntb: Add mutex to make link_event_callback executed linearly.
Date: Mon, 25 Aug 2025 08:06:22 -0700 [thread overview]
Message-ID: <483cc0f8-6caa-4124-a724-433ff0d798fa@intel.com> (raw)
In-Reply-To: <aKwpnFtdtBlDv69O@didi-ThinkCentre-M930t-N000>
On 8/25/25 2:15 AM, fuyuanli wrote:
> Since the CPU selected by schedule_work is uncertain, multiple link_event
> callbacks may be executed at same time. For example, after peer's link is
> up, it is down quickly before local link_work completed. If link_cleanup
> is added to the workqueue of another CPU, then link_work and link_cleanup
> may be executed at the same time. So add a mutex to prevent them from being
> executed concurrently.
>
> Signed-off-by: fuyuanli <fuyuanli@didiglobal.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> v2:
> 1) use guard() instead of lock & unlock functions.
>
> v1:
> Link: https://lore.kernel.org/all/aKiBi4ZDlbgzed%2Fz@didi-ThinkCentre-M930t-N000/
> ---
> drivers/ntb/ntb_transport.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/ntb/ntb_transport.c b/drivers/ntb/ntb_transport.c
> index 4f775c3e218f..eb875e3db2e3 100644
> --- a/drivers/ntb/ntb_transport.c
> +++ b/drivers/ntb/ntb_transport.c
> @@ -59,6 +59,7 @@
> #include <linux/slab.h>
> #include <linux/types.h>
> #include <linux/uaccess.h>
> +#include <linux/mutex.h>
> #include "linux/ntb.h"
> #include "linux/ntb_transport.h"
>
> @@ -241,6 +242,9 @@ struct ntb_transport_ctx {
> struct work_struct link_cleanup;
>
> struct dentry *debugfs_node_dir;
> +
> + /* Make sure workq of link event be executed serially */
> + struct mutex link_event_lock;
> };
>
> enum {
> @@ -1024,6 +1028,7 @@ static void ntb_transport_link_cleanup_work(struct work_struct *work)
> struct ntb_transport_ctx *nt =
> container_of(work, struct ntb_transport_ctx, link_cleanup);
>
> + guard(mutex)(&nt->link_event_lock);
> ntb_transport_link_cleanup(nt);
> }
>
> @@ -1047,6 +1052,8 @@ static void ntb_transport_link_work(struct work_struct *work)
> u32 val;
> int rc = 0, i, spad;
>
> + guard(mutex)(&nt->link_event_lock);
> +
> /* send the local info, in the opposite order of the way we read it */
>
> if (nt->use_msi) {
next prev parent reply other threads:[~2025-08-25 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 9:15 fuyuanli
2025-08-25 15:06 ` Dave Jiang [this message]
2025-09-03 2:20 ` yuanli fu
2025-09-03 15:26 ` Dave Jiang
2025-08-25 16:18 ` Logan Gunthorpe
2025-09-30 6:50 ` yuanli fu
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=483cc0f8-6caa-4124-a724-433ff0d798fa@intel.com \
--to=dave.jiang@intel.com \
--cc=allenbh@gmail.com \
--cc=fuyuanli0722@gmail.com \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=ntb@lists.linux.dev \
/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®