From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, angus.chen@jaguarmicro.com, idosch@idosch.org,
syzbot+a5e719ac7c268e414c95@syzkaller.appspotmail.com,
syzbot+a03fd670838d927d9cd8@syzkaller.appspotmail.com
Subject: Re: [PATCH net-next] Revert "net: Remove low_thresh in ip defrag"
Date: Wed, 17 May 2023 04:00:19 +0000 [thread overview]
Message-ID: <168429601989.23839.7156354882761941176.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230517034112.1261835-1-kuba@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 16 May 2023 20:41:12 -0700 you wrote:
> This reverts commit b2cbac9b9b28730e9e53be20b6cdf979d3b9f27e.
>
> We have multiple reports of obvious breakage from this patch.
>
> Reported-by: Ido Schimmel <idosch@idosch.org>
> Link: https://lore.kernel.org/all/ZGIRWjNcfqI8yY8W@shredder/
> Link: https://lore.kernel.org/all/CADJHv_sDK=0RrMA2FTZQV5fw7UQ+qY=HG21Wu5qb0V9vvx5w6A@mail.gmail.com/
> Reported-by: syzbot+a5e719ac7c268e414c95@syzkaller.appspotmail.com
> Reported-by: syzbot+a03fd670838d927d9cd8@syzkaller.appspotmail.com
> Fixes: b2cbac9b9b28 ("net: Remove low_thresh in ip defrag")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
> [...]
Here is the summary with links:
- [net-next] Revert "net: Remove low_thresh in ip defrag"
https://git.kernel.org/bpf/bpf-next/c/e7480a44d7c4
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:[~2023-05-17 4:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 3:41 [PATCH net-next] Revert "net: Remove low_thresh in ip defrag" Jakub Kicinski
2023-05-17 4:00 ` 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=168429601989.23839.7156354882761941176.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=angus.chen@jaguarmicro.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@idosch.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+a03fd670838d927d9cd8@syzkaller.appspotmail.com \
--cc=syzbot+a5e719ac7c268e414c95@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 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.