From: patchwork-bot+netdevbpf@kernel.org
To: Vasily Averin <vvs@virtuozzo.com>
Cc: willemdebruijn.kernel@gmail.com, davem@davemloft.net,
kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2] net: drop bogus skb with CHECKSUM_PARTIAL and offset beyond end of trimmed packet
Date: Tue, 15 Dec 2020 03:10:48 +0000 [thread overview]
Message-ID: <160800184824.22481.2756487220504358038.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1b2494af-2c56-8ee2-7bc0-923fcad1cdf8@virtuozzo.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 14 Dec 2020 22:07:39 +0300 you wrote:
> syzbot reproduces BUG_ON in skb_checksum_help():
> tun creates (bogus) skb with huge partial-checksummed area and
> small ip packet inside. Then ip_rcv trims the skb based on size
> of internal ip packet, after that csum offset points beyond of
> trimmed skb. Then checksum_tg() called via netfilter hook
> triggers BUG_ON:
>
> [...]
Here is the summary with links:
- [v2] net: drop bogus skb with CHECKSUM_PARTIAL and offset beyond end of trimmed packet
https://git.kernel.org/netdev/net-next/c/54970a2fbb67
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:[~2020-12-15 3:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 15:00 [PATCH] net: check skb partial checksum offset after trim Vasily Averin
2020-12-11 15:37 ` Vasily Averin
2020-12-12 8:29 ` Vasily Averin
2020-12-12 23:49 ` Willem de Bruijn
2020-12-13 19:37 ` Vasily Averin
2020-12-14 1:59 ` Willem de Bruijn
2020-12-14 19:07 ` [PATCH v2] net: drop bogus skb with CHECKSUM_PARTIAL and offset beyond end of trimmed packet Vasily Averin
2020-12-14 20:59 ` Willem de Bruijn
2020-12-15 3:10 ` patchwork-bot+netdevbpf [this message]
2020-12-14 20:54 ` [PATCH] net: check skb partial checksum offset after trim Jakub Kicinski
2020-12-14 21:07 ` Willem de Bruijn
2020-12-15 5:42 ` Vasily Averin
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=160800184824.22481.2756487220504358038.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vvs@virtuozzo.com \
--cc=willemdebruijn.kernel@gmail.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.