From: patchwork-bot+netdevbpf@kernel.org
To: Ren Wei <n05ec@lzu.edu.cn>
Cc: netdev@vger.kernel.org, yotam.gi@gmail.com, jhs@mojatatu.com,
davem@davemloft.net, xiyou.wangcong@gmail.com, kuba@kernel.org,
victor@mojatatu.com, yuantan098@gmail.com, bird@lzu.edu.cn,
edragain@163.com
Subject: Re: [PATCH 1/2] net: ife: require ETH_HLEN to be pullable in ife_decode()
Date: Sun, 14 Jun 2026 00:50:07 +0000 [thread overview]
Message-ID: <178139820714.1641091.2899241191922395715.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260610183814.1648888-2-n05ec@lzu.edu.cn>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 11 Jun 2026 02:37:43 +0800 you wrote:
> From: Yong Wang <edragain@163.com>
>
> ife decode may return after making only the outer IFE header and
> metadata pullable. The caller then passes the decapsulated packet to
> eth_type_trans(), which expects the inner Ethernet header to be
> accessible from the linear data area.
>
> [...]
Here is the summary with links:
- [1/2] net: ife: require ETH_HLEN to be pullable in ife_decode()
https://git.kernel.org/netdev/net/c/9406f6012b73
- [2/2] selftests/tc-testing: Verify IFE can handle truncated inner Ethernet header
https://git.kernel.org/netdev/net/c/a4004aa0debf
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-06-14 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260610183814.1648888-1-n05ec@lzu.edu.cn>
2026-06-10 18:37 ` [PATCH 1/2] net: ife: require ETH_HLEN to be pullable in ife_decode() Ren Wei
2026-06-14 0:50 ` patchwork-bot+netdevbpf [this message]
2026-06-10 18:37 ` [PATCH 2/2] selftests/tc-testing: Verify IFE can handle truncated inner Ethernet header Ren Wei
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=178139820714.1641091.2899241191922395715.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bird@lzu.edu.cn \
--cc=davem@davemloft.net \
--cc=edragain@163.com \
--cc=jhs@mojatatu.com \
--cc=kuba@kernel.org \
--cc=n05ec@lzu.edu.cn \
--cc=netdev@vger.kernel.org \
--cc=victor@mojatatu.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yotam.gi@gmail.com \
--cc=yuantan098@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