From: patchwork-bot+netdevbpf@kernel.org
To: Kalpesh Solanki <skalpesh942@gmail.com>
Cc: willemdebruijn.kernel@gmail.com, jasowangio@gmail.com,
jk@ozlabs.org, matt@codeconstruct.com.au, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tun: disallow setting ARPHRD_MCTP link type via TUNSETLINK
Date: Wed, 18 Nov 2026 02:20:04 +0000 [thread overview]
Message-ID: <179496840454.1411964.2818262145565407284.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261112131056.234801-1-skalpesh942@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 12 Nov 2026 18:40:55 +0530 you wrote:
> When an IFF_TUN device is registered as ARPHRD_NONE, mctp_register()
> attaches an mctp_dev context to it. For ARPHRD_NONE and ARPHRD_LOOPBACK
> devices, incoming packets in mctp_pkttype_receive() invoke __mctp_cb(skb),
> which initializes cb->magic = 0x4d435450 and zeros cb->halen.
>
> If a userspace process sets the link type of the TUN device to ARPHRD_MCTP
> via ioctl(fd, TUNSETLINK, ARPHRD_MCTP) and transmits a frame carrying
> protocol ETH_P_MCTP, mctp_pkttype_receive() evaluates dev->type ==
> ARPHRD_MCTP and calls mctp_cb(skb). Because frames allocated in
> tun_get_user() have a cleared skb->cb and were not constructed by an MCTP
> hardware driver, mctp_cb() trips:
>
> [...]
Here is the summary with links:
- tun: disallow setting ARPHRD_MCTP link type via TUNSETLINK
https://git.kernel.org/netdev/net/c/0a3778b93be4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-18 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 13:10 Kalpesh Solanki
2026-11-12 13:16 ` netdev-bot+sinfo
2026-11-12 13:22 ` KALPESH SOLANKI
2026-11-18 2:20 ` patchwork-bot+netdevbpf [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=179496840454.1411964.2818262145565407284.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=jasowangio@gmail.com \
--cc=jk@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=skalpesh942@gmail.com \
--cc=willemdebruijn.kernel@gmail.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®