From: patchwork-bot+netdevbpf@kernel.org
To: Marco Elver <elver@google.com>
Cc: linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
davem@davemloft.net, kuba@kernel.org, jonathan.lemon@gmail.com,
willemb@google.com, linmiaohe@huawei.com, gnault@redhat.com,
dseok.yi@samsung.com, kyk.segfault@gmail.com,
viro@zeniv.linux.org.uk, netdev@vger.kernel.org,
glider@google.com,
syzbot+7b99aafdcc2eedea6178@syzkaller.appspotmail.com,
edumazet@google.com
Subject: Re: [PATCH net-next] net: fix up truesize of cloned skb in skb_prepare_for_shift()
Date: Wed, 03 Feb 2021 02:00:10 +0000 [thread overview]
Message-ID: <161231761089.3354.12212298299944124109.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210201160420.2826895-1-elver@google.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 1 Feb 2021 17:04:20 +0100 you wrote:
> Avoid the assumption that ksize(kmalloc(S)) == ksize(kmalloc(S)): when
> cloning an skb, save and restore truesize after pskb_expand_head(). This
> can occur if the allocator decides to service an allocation of the same
> size differently (e.g. use a different size class, or pass the
> allocation on to KFENCE).
>
> Because truesize is used for bookkeeping (such as sk_wmem_queued), a
> modified truesize of a cloned skb may result in corrupt bookkeeping and
> relevant warnings (such as in sk_stream_kill_queues()).
>
> [...]
Here is the summary with links:
- [net-next] net: fix up truesize of cloned skb in skb_prepare_for_shift()
https://git.kernel.org/netdev/net-next/c/097b9146c0e2
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:[~2021-02-03 2:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 16:04 [PATCH net-next] net: fix up truesize of cloned skb in skb_prepare_for_shift() Marco Elver
2021-02-01 16:50 ` Christoph Paasch
2021-02-01 17:33 ` Marco Elver
2021-02-01 17:58 ` Eric Dumazet
2021-02-02 16:58 ` Christoph Paasch
2021-02-02 17:59 ` Eric Dumazet
2021-02-02 18:34 ` Marco Elver
2021-02-03 2: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=161231761089.3354.12212298299944124109.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dseok.yi@samsung.com \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=gnault@redhat.com \
--cc=jonathan.lemon@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=kuba@kernel.org \
--cc=kyk.segfault@gmail.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+7b99aafdcc2eedea6178@syzkaller.appspotmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).