From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
elver@google.com, edumazet@google.com
Subject: Re: [PATCH net-next 0/2] tcp: take care of another syzbot issue
Date: Wed, 23 Feb 2022 04:10:10 +0000 [thread overview]
Message-ID: <164558941044.26093.15086204600598443366.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220222032113.4005821-1-eric.dumazet@gmail.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 21 Feb 2022 19:21:11 -0800 you wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> This is a minor issue: It took months for syzbot to find a C repro,
> and even with it, I had to spend a lot of time to understand KFENCE
> was a prereq. With the default kfence 500ms interval, I had to be
> very patient to trigger the kernel warning and perform my analysis.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: add skb_set_end_offset() helper
https://git.kernel.org/netdev/net-next/c/763087dab975
- [net-next,2/2] net: preserve skb_end_offset() in skb_unclone_keeptruesize()
(no matching commit)
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:[~2022-02-23 4:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 3:21 [PATCH net-next 0/2] tcp: take care of another syzbot issue Eric Dumazet
2022-02-22 3:21 ` [PATCH net-next 1/2] net: add skb_set_end_offset() helper Eric Dumazet
2022-02-22 3:21 ` [PATCH net-next 2/2] net: preserve skb_end_offset() in skb_unclone_keeptruesize() Eric Dumazet
2022-02-23 9:25 ` Marco Elver
2022-02-23 4:10 ` patchwork-bot+netdevbpf [this message]
2022-02-23 4:15 ` [PATCH net-next 0/2] tcp: take care of another syzbot issue Jakub Kicinski
2022-02-23 4:48 ` Eric Dumazet
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=164558941044.26093.15086204600598443366.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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