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
| ||
|
Date: Thu, 22 Sep 2022 14:10:16 +0000 From: patchwork-bot+netdevbpf@...nel.org To: Sean Anderson <seanga2@...il.com> Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, nbowler@...conx.ca, eike-kernel@...tec.de, zheyuma97@...il.com, andrew@...n.ch Subject: Re: [PATCH net v2] net: sunhme: Fix packet reception for len < RX_COPY_THRESHOLD Hello: This patch was applied to netdev/net.git (master) by Jakub Kicinski <kuba@...nel.org>: On Tue, 20 Sep 2022 19:50:18 -0400 you wrote: > There is a separate receive path for small packets (under 256 bytes). > Instead of allocating a new dma-capable skb to be used for the next packet, > this path allocates a skb and copies the data into it (reusing the existing > sbk for the next packet). There are two bytes of junk data at the beginning > of every packet. I believe these are inserted in order to allow aligned DMA > and IP headers. We skip over them using skb_reserve. Before copying over > the data, we must use a barrier to ensure we see the whole packet. The > current code only synchronizes len bytes, starting from the beginning of > the packet, including the junk bytes. However, this leaves off the final > two bytes in the packet. Synchronize the whole packet. > > [...] Here is the summary with links: - [net,v2] net: sunhme: Fix packet reception for len < RX_COPY_THRESHOLD https://git.kernel.org/netdev/net/c/878e2405710a You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists