All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: jgg@ziepe.ca, linux-kernel@vger.kernel.org,
	linux-rdma@vger.kernel.org, rolandd@cisco.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] RDMA/core: Fix member use-after-free in process_group_error()
Date: Wed, 23 Sep 2026 11:47:52 +0300	[thread overview]
Message-ID: <20260923084752.GN563127@unreal> (raw)
In-Reply-To: <20260916184555.2093238-1-vulab@iscas.ac.cn>

On Wed, Sep 16, 2026 at 06:45:55PM +0000, Wentao Liang wrote:
> If the callback on the error path returns non-zero after a concurrent
> ib_sa_free_multicast() already dropped the initial member reference,
> dropping our temporary reference completes the waiter, which then frees
> the member before ib_sa_free_multicast() dereferences it again.
> 
> Only free the multicast member when our reference decrement was not
> the last one; otherwise the concurrent free is already in flight.

I'm not sure that last sentence is correct. Can you prove it?
Because we have the following code:
  662 void ib_sa_free_multicast(struct ib_sa_multicast *multicast)
  663 {
  ...
  685
  686         deref_member(member);
  687         wait_for_completion(&member->comp);
  ...
  691 EXPORT_SYMBOL(ib_sa_free_multicast);

Thanks

> 
> Fixes: faec2f7b96b5 ("IB/sa: Track multicast join/leave requests")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
>  drivers/infiniband/core/multicast.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/infiniband/core/multicast.c b/drivers/infiniband/core/multicast.c
> index bea7df3dd8f3..aa6fdac5fcde 100644
> --- a/drivers/infiniband/core/multicast.c
> +++ b/drivers/infiniband/core/multicast.c
> @@ -409,8 +409,9 @@ static void process_group_error(struct mcast_group *group)
>  
>  		ret = member->multicast.callback(-ENETRESET,
>  						 &member->multicast);
> -		deref_member(member);
> -		if (ret)
> +		if (refcount_dec_and_test(&member->refcount))
> +			complete(&member->comp);
> +		else if (ret)
>  			ib_sa_free_multicast(&member->multicast);
>  		spin_lock_irq(&group->lock);
>  	}
> -- 
> 2.34.1
> 

      parent reply	other threads:[~2026-09-23  8:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 18:45 [PATCH] RDMA/core: Fix member use-after-free in process_group_error() Wentao Liang
2026-09-16 18:55 ` sashiko-bot
2026-09-23  8:47 ` Leon Romanovsky [this message]

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=20260923084752.GN563127@unreal \
    --to=leon@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rolandd@cisco.com \
    --cc=stable@vger.kernel.org \
    --cc=vulab@iscas.ac.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.