From: Jakub Kicinski <kuba@kernel.org>
To: Chengfeng Ye <dg573847474@gmail.com>
Cc: jeremy@codeconstruct.com.au, matt@codeconstruct.com.au,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mctp: route: hold key->lock in mctp_flow_prepare_output()
Date: Wed, 4 Mar 2026 17:52:07 -0800 [thread overview]
Message-ID: <20260304175207.34579d99@kernel.org> (raw)
In-Reply-To: <20260302174056.796540-1-dg573847474@gmail.com>
On Mon, 2 Mar 2026 17:40:56 +0000 Chengfeng Ye wrote:
> mctp_flow_prepare_output() checks key->dev and may call
> mctp_dev_set_key(), but it does not hold key->lock while doing so.
Please add an appropriate Fixes tag and repost.
--
pw-bot: cr
next prev parent reply other threads:[~2026-03-05 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 17:40 [PATCH] mctp: route: hold key->lock in mctp_flow_prepare_output() Chengfeng Ye
2026-03-05 1:52 ` Jakub Kicinski [this message]
2026-03-06 0:24 ` Jeremy Kerr
2026-03-06 3:25 ` Chengfeng Ye
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=20260304175207.34579d99@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dg573847474@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jeremy@codeconstruct.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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