Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net v3] ipv4,
 ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <169618082300.17513.8154196586548656981.git-patchwork-notify@kernel.org>
Date:   Sun, 01 Oct 2023 17:20:23 +0000
References: <730408.1695292879@warthog.procyon.org.uk>
In-Reply-To: <730408.1695292879@warthog.procyon.org.uk>
To:     David Howells <dhowells@redhat.com>
Cc:     netdev@vger.kernel.org,
        syzbot+62cbf263225ae13ff153@syzkaller.appspotmail.com,
        edumazet@google.com, willemdebruijn.kernel@gmail.com,
        davem@davemloft.net, dsahern@kernel.org, pabeni@redhat.com,
        kuba@kernel.org, bpf@vger.kernel.org,
        syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Thu, 21 Sep 2023 11:41:19 +0100 you wrote:
> Including the transhdrlen in length is a problem when the packet is
> partially filled (e.g. something like send(MSG_MORE) happened previously)
> when appending to an IPv4 or IPv6 packet as we don't want to repeat the
> transport header or account for it twice.  This can happen under some
> circumstances, such as splicing into an L2TP socket.
> 
> The symptom observed is a warning in __ip6_append_data():
> 
> [...]

Here is the summary with links:
  - [net,v3] ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()
    https://git.kernel.org/netdev/net/c/9d4c75800f61

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