From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Hui Peng <benquike@gmail.com>,
matt@codeconstruct.com.au, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Cc: horms@kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mctp: route: verify socket ownership in mctp_lookup_prealloc_tag()
Date: Sun, 20 Sep 2026 16:38:58 +0800 [thread overview]
Message-ID: <159f68ef9444f8b44a6d5764de8696f094fa889d.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20260919212851.3240598-1-benquike@gmail.com>
Hi Hui,
> When a socket transmits a packet with `MCTP_TAG_PREALLOC` set,
> mctp_lookup_prealloc_tag() iterates over the per-netns `&mns->keys`
> list and matches `netid`, `req_tag`, `peer_addr`, and `manual_alloc`,
> but omits checking whether `tmp->sk == &msk->sk`.
OK, good catch.
> Verify `tmp->sk == &msk->sk` in `mctp_lookup_prealloc_tag()`.
Or we could instead iterate the socket's tag list?
Cheers,
Jeremy
prev parent reply other threads:[~2026-09-20 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 21:28 Hui Peng
2026-09-20 8:38 ` Jeremy Kerr [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=159f68ef9444f8b44a6d5764de8696f094fa889d.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=benquike@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--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
all inboxes | Powered by JetHome®