All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xiang Mei <xmei5@asu.edu>
Cc: subash.a.kasiviswanathan@oss.qualcomm.com,
	sean.tranchetti@oss.qualcomm.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, co+4638111fe2a12980@bugs.sh
Subject: Re: [PATCH net v2] net: qualcomm: rmnet: restore skb->dev on deaggregated frames
Date: Mon, 24 Aug 2026 18:50:17 +0000	[thread overview]
Message-ID: <178759741799.3062482.15686763886179126811.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260820195240.1631458-1-xmei5@asu.edu>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 20 Aug 2026 12:52:40 -0700 you wrote:
> rmnet_map_deaggregate() allocates each sub-frame with alloc_skb() and
> leaves skb->dev NULL. __rmnet_map_ingress_handler() assigns
> skb->dev = ep->egress_dev only on the data path, but a MAP command frame
> is dispatched to rmnet_map_command() before that, so rmnet_map_send_ack()
> runs netif_tx_lock(skb->dev) on a NULL device. An unprivileged user
> reaches this by unsharing a user+net namespace, creating an rmnet link
> over a tap device with INGRESS_DEAGGREGATION and INGRESS_MAP_COMMANDS,
> and writing an aggregated frame carrying a flow-control command to the
> tap fd.
> 
> [...]

Here is the summary with links:
  - [net,v2] net: qualcomm: rmnet: restore skb->dev on deaggregated frames
    https://git.kernel.org/netdev/net/c/a66734a1c5e3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-24 18:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 19:52 [PATCH net v2] net: qualcomm: rmnet: restore skb->dev on deaggregated frames Xiang Mei
2026-08-20 20:39 ` subash.a.kasiviswanathan
2026-08-24 18:50 ` 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=178759741799.3062482.15686763886179126811.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=co+4638111fe2a12980@bugs.sh \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sean.tranchetti@oss.qualcomm.com \
    --cc=subash.a.kasiviswanathan@oss.qualcomm.com \
    --cc=xmei5@asu.edu \
    /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.