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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 29 Oct 2022 15:45:15 +0000 From: Eric Dumazet <edumazet@...gle.com> To: "David S . Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com> Cc: netdev@...r.kernel.org, eric.dumazet@...il.com, Eric Dumazet <edumazet@...gle.com> Subject: [PATCH v2 net-next 0/5] inet: add drop monitor support I recently tried to analyse flakes in ip_defrag selftest. This failed miserably. IPv4 and IPv6 reassembly units are causing false kfree_skb() notifications. It is time to deal with this issue. First two patches are changing core networking to better deal with eventual skb frag_list chains, in respect of kfree_skb/consume_skb status. Last three patches are adding three new drop reasons, and make sure skbs that have been reassembled into a large datagram are no longer viewed as dropped ones. After this, understanding why ip_defrag selftest is flaky is possible using standard drop monitoring tools. v2: fix kdoc warning (Jakub) Eric Dumazet (5): net: dropreason: add SKB_CONSUMED reason net: dropreason: propagate drop_reason to skb_release_data() net: dropreason: add SKB_DROP_REASON_DUP_FRAG net: dropreason: add SKB_DROP_REASON_FRAG_REASM_TIMEOUT net: dropreason: add SKB_DROP_REASON_FRAG_TOO_FAR include/net/dropreason.h | 14 ++++++++++++ include/net/inet_frag.h | 6 ++++- include/net/ipv6_frag.h | 3 ++- net/core/skbuff.c | 30 ++++++++++++++----------- net/ipv4/inet_fragment.c | 14 ++++++++---- net/ipv4/ip_fragment.c | 19 +++++++++++----- net/ipv6/netfilter/nf_conntrack_reasm.c | 2 +- net/ipv6/reassembly.c | 13 +++++++---- 8 files changed, 71 insertions(+), 30 deletions(-) -- 2.38.1.273.g43a17bfeac-goog
Powered by blists - more mailing lists