public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexandra Winter <wintera@linux.ibm.com>
To: Wen Gu <guwen@linux.alibaba.com>,
	wenjia@linux.ibm.com, jaka@linux.ibm.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Cc: alibuda@linux.alibaba.com, tonylu@linux.alibaba.com,
	horms@kernel.org, linux-rdma@vger.kernel.org,
	linux-s390@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 2/2] net/smc: fix LGR and link use-after-free issue
Date: Fri, 22 Nov 2024 17:11:59 +0100	[thread overview]
Message-ID: <1e153fb1-d4ac-4c25-ab76-94361a118a37@linux.ibm.com> (raw)
In-Reply-To: <5688fe46-dda0-4050-ba24-eb5ef573f120@linux.ibm.com>



On 22.11.24 17:03, Alexandra Winter wrote:
> Are you sure that all callers of smc_conn_free(), that are not smc_conn_abort(), do set the socklock?
> It seems to me that the path of smc_conn_kill() is not covered by your solution.

My bad. smc_conn_kill() is called under socklock

  reply	other threads:[~2024-11-22 16:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-22  7:16 [PATCH net 0/2] two fixes for SMC Wen Gu
2024-11-22  7:16 ` [PATCH net 1/2] net/smc: initialize close_work early to avoid warning Wen Gu
2024-11-22 15:56   ` Wenjia Zhang
2024-11-22 16:17   ` Alexandra Winter
2024-11-22  7:16 ` [PATCH net 2/2] net/smc: fix LGR and link use-after-free issue Wen Gu
2024-11-22 15:56   ` Wenjia Zhang
2024-11-25  6:46     ` Wen Gu
2024-11-26 12:12       ` Wenjia Zhang
2024-11-26 12:19         ` Wenjia Zhang
2024-11-22 16:03   ` Alexandra Winter
2024-11-22 16:11     ` Alexandra Winter [this message]
2024-11-25 10:00     ` Wen Gu
2024-11-25 13:02       ` Alexandra Winter
2024-11-27  7:03         ` Wen Gu

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=1e153fb1-d4ac-4c25-ab76-94361a118a37@linux.ibm.com \
    --to=wintera@linux.ibm.com \
    --cc=alibuda@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=guwen@linux.alibaba.com \
    --cc=horms@kernel.org \
    --cc=jaka@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tonylu@linux.alibaba.com \
    --cc=wenjia@linux.ibm.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