From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, willemb@google.com, edumazet@google.com
Subject: Re: [PATCH v2 net 0/3] net: af_packet: be careful when expanding mac header size
Date: Thu, 02 Jun 2022 18:20:14 +0000 [thread overview]
Message-ID: <165419401442.24492.16341541730612381725.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220602161859.2546399-1-eric.dumazet@gmail.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 2 Jun 2022 09:18:56 -0700 you wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> A recent regression in af_packet needed a preliminary debug patch,
> which will presumably be useful for next bugs hunting.
>
> The af_packet fix is to make sure MAC headers are contained in
> skb linear part, as GSO stack requests.
>
> [...]
Here is the summary with links:
- [v2,net,1/3] net: CONFIG_DEBUG_NET depends on CONFIG_NET
https://git.kernel.org/netdev/net/c/eb0b39efb7d9
- [v2,net,2/3] net: add debug info to __skb_pull()
https://git.kernel.org/netdev/net/c/22296a5c0cd3
- [v2,net,3/3] net/af_packet: make sure to pull mac header
https://git.kernel.org/netdev/net/c/e9d3f80935b6
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:[~2022-06-02 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 16:18 [PATCH v2 net 0/3] net: af_packet: be careful when expanding mac header size Eric Dumazet
2022-06-02 16:18 ` [PATCH v2 net 1/3] net: CONFIG_DEBUG_NET depends on CONFIG_NET Eric Dumazet
2022-06-02 16:18 ` [PATCH v2 net 2/3] net: add debug info to __skb_pull() Eric Dumazet
2022-06-02 16:18 ` [PATCH v2 net 3/3] net/af_packet: make sure to pull mac header Eric Dumazet
2022-06-02 19:49 ` Michael S. Tsirkin
2022-06-02 18: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=165419401442.24492.16341541730612381725.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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.