From: Eric Dumazet <eric.dumazet@gmail.com>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: netdev <netdev@vger.kernel.org>, Marco Elver <elver@google.com>,
Eric Dumazet <edumazet@google.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: [PATCH net-next 0/2] tcp: take care of another syzbot issue
Date: Mon, 21 Feb 2022 19:21:11 -0800 [thread overview]
Message-ID: <20220222032113.4005821-1-eric.dumazet@gmail.com> (raw)
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.
This series targets net-next tree, because I added a new generic helper
in the first patch, then fixed the issue in the second one.
They can be backported once proven solid.
Eric Dumazet (2):
net: add skb_set_end_offset() helper
net: preserve skb_end_offset() in skb_unclone_keeptruesize()
include/linux/skbuff.h | 30 +++++++++++++++++--------
net/core/skbuff.c | 51 ++++++++++++++++++++++++++++++------------
2 files changed, 58 insertions(+), 23 deletions(-)
--
2.35.1.473.g83b2b277ed-goog
next reply other threads:[~2022-02-22 3:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 3:21 Eric Dumazet [this message]
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 ` [PATCH net-next 0/2] tcp: take care of another syzbot issue patchwork-bot+netdevbpf
2022-02-23 4:15 ` 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=20220222032113.4005821-1-eric.dumazet@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elver@google.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