netdev - Re: [PATCH net-next v3] net: avoid double accounting for pure zerocopy skbs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <163594860815.30241.9867591652285399304.git-patchwork-notify@kernel.org>
Date:   Wed, 03 Nov 2021 14:10:08 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Talal Ahmad <mailtalalahmad@...il.com>
Cc:     davem@...emloft.net, netdev@...r.kernel.org, arjunroy@...gle.com,
        edumazet@...gle.com, soheil@...gle.com, willemb@...gle.com,
        dsahern@...nel.org, yoshfuji@...ux-ipv6.org, kuba@...nel.org,
        cong.wang@...edance.com, haokexin@...il.com,
        jonathan.lemon@...il.com, alobakin@...me, pabeni@...hat.com,
        ilias.apalodimas@...aro.org, memxor@...il.com, elver@...gle.com,
        nogikh@...gle.com, vvs@...tuozzo.com, talalahmad@...gle.com
Subject: Re: [PATCH net-next v3] net: avoid double accounting for pure zerocopy
 skbs

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@...emloft.net>:

On Tue,  2 Nov 2021 22:58:44 -0400 you wrote:
> From: Talal Ahmad <talalahmad@...gle.com>
> 
> Track skbs containing only zerocopy data and avoid charging them to
> kernel memory to correctly account the memory utilization for
> msg_zerocopy. All of the data in such skbs is held in user pages which
> are already accounted to user. Before this change, they are charged
> again in kernel in __zerocopy_sg_from_iter. The charging in kernel is
> excessive because data is not being copied into skb frags. This
> excessive charging can lead to kernel going into memory pressure
> state which impacts all sockets in the system adversely. Mark pure
> zerocopy skbs with a SKBFL_PURE_ZEROCOPY flag and remove
> charge/uncharge for data in such skbs.
> 
> [...]

Here is the summary with links:
  - [net-next,v3] net: avoid double accounting for pure zerocopy skbs
    https://git.kernel.org/netdev/net/c/9b65b17db723

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html