All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Rongguang Wei <clementwei90@163.com>
Cc: willemdebruijn.kernel@gmail.com, kuba@kernel.org,
	jasowangio@gmail.com, andrew+netdev@lunn.ch,
	netdev@vger.kernel.org, weirongguang@kylinos.cn,
	willemb@google.com
Subject: Re: [PATCH net v2] tap: fix incorrect variable used for USO check in set_offload()
Date: Mon, 10 Aug 2026 23:40:13 +0000	[thread overview]
Message-ID: <178640521338.254991.9428922162633399342.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260807070914.112698-1-clementwei90@163.com>

Hello:

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

On Fri,  7 Aug 2026 15:09:14 +0800 you wrote:
> From: Rongguang Wei <weirongguang@kylinos.cn>
> 
> The USO features in set_offload() incorrectly uses feature_mask and
> features argument.
> 
> The USO feature was written to the local features variable instead of
> feature_mask. All other offload bits (TSO, TSO_ECN) are stored in
> feature_mask which becomes tap->tap_features and is used by
> tap_handle_frame() for GSO segmentation. Without NETIF_F_GSO_UDP_L4
> in tap->tap_features, making USO on tap effectively non-functional.
> 
> [...]

Here is the summary with links:
  - [net,v2] tap: fix incorrect variable used for USO check in set_offload()
    https://git.kernel.org/netdev/net-next/c/fac7973f004d

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-10 23:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07  7:09 [PATCH net v2] tap: fix incorrect variable used for USO check in set_offload() Rongguang Wei
2026-08-08 15:39 ` Willem de Bruijn
2026-08-10  1:10   ` Rongguang Wei
2026-08-10  2:00   ` Rongguang Wei
2026-08-10 19:55     ` Willem de Bruijn
2026-08-10 23:40 ` 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=178640521338.254991.9428922162633399342.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=clementwei90@163.com \
    --cc=jasowangio@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=weirongguang@kylinos.cn \
    --cc=willemb@google.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 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.