diff options
| author |   Jakub Kicinski <kuba@kernel.org> | 2022-10-31 20:14:30 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2022-10-31 20:14:30 -0700 |
| commit | 6f1a298b2e24c703bfcc643e41bc7c0604fe4830 (patch) | |
| tree | 042e3e6a4c27c96c782f403bd60b1eec3780b3bb /net/netfilter/nft_objref.c | |
| parent | net: systemport: Add support for RDMA overflow statistic counter (diff) | |
| parent | net: dropreason: add SKB_DROP_REASON_FRAG_TOO_FAR (diff) | |
| download | wireguard-linux-6f1a298b2e24c703bfcc643e41bc7c0604fe4830.tar.xz wireguard-linux-6f1a298b2e24c703bfcc643e41bc7c0604fe4830.zip | |
Merge branch 'inet-add-drop-monitor-support'
Eric Dumazet says:
====================
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.
====================
Link: https://lore.kernel.org/r/20221029154520.2747444-1-edumazet@google.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net/netfilter/nft_objref.c')
0 files changed, 0 insertions, 0 deletions