From: patchwork-bot+netdevbpf@kernel.org
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, edumazet@google.com, horms@kernel.org,
syzbot+99d15fcdb0132a1e1a82@syzkaller.appspotmail.com
Subject: Re: [PATCH net v2] net: mpls: error out if inner headers are not set
Date: Sat, 24 Feb 2024 02:10:29 +0000 [thread overview]
Message-ID: <170874062935.5601.1311290697565705511.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240222140321.14080-1-fw@strlen.de>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 22 Feb 2024 15:03:10 +0100 you wrote:
> mpls_gso_segment() assumes skb_inner_network_header() returns
> a valid result:
>
> mpls_hlen = skb_inner_network_header(skb) - skb_network_header(skb);
> if (unlikely(!mpls_hlen || mpls_hlen % MPLS_HLEN))
> goto out;
> if (unlikely(!pskb_may_pull(skb, mpls_hlen)))
>
> [...]
Here is the summary with links:
- [net,v2] net: mpls: error out if inner headers are not set
https://git.kernel.org/netdev/net-next/c/025f8ad20f2e
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:[~2024-02-24 2:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 12:33 [syzbot] [net?] WARNING in mpls_gso_segment syzbot
2024-02-21 13:15 ` Florian Westphal
2024-02-22 8:14 ` Eric Dumazet
2024-02-22 12:23 ` Florian Westphal
2024-02-22 12:29 ` Eric Dumazet
2024-02-22 12:57 ` Florian Westphal
2024-02-22 13:27 ` Eric Dumazet
2024-02-22 14:03 ` [PATCH net v2] net: mpls: error out if inner headers are not set Florian Westphal
2024-02-23 3:33 ` Jakub Kicinski
2024-02-23 7:08 ` Florian Westphal
2024-02-24 2:10 ` patchwork-bot+netdevbpf [this message]
2024-02-22 4:00 ` [PATCH net-next] net/mpls: fix WARNING in mpls_gso_segment Lizhi Xu
2024-02-22 8:11 ` Eric Dumazet
2024-02-23 3:30 ` Lizhi Xu
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=170874062935.5601.1311290697565705511.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+99d15fcdb0132a1e1a82@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).