Files
Antoine Tenart db4ce5d04b net: track pfmemalloc drops via SKB_DROP_REASON_PFMEMALLOC
JIRA: https://issues.redhat.com/browse/RHEL-139236
Upstream Status: linux.git
Conflicts:\
- Context difference due to missing upstream commit b0e214d21203 ("netfilter:
  keep conntrack reference until IPsecv6 policy checks are done") in c9s.

commit a6f190630d070173897a7e98a30188b7638ba0a1
Author: Jesper Dangaard Brouer <hawk@kernel.org>
Date:   Wed Jul 16 18:26:53 2025 +0200

    net: track pfmemalloc drops via SKB_DROP_REASON_PFMEMALLOC

    Add a new SKB drop reason (SKB_DROP_REASON_PFMEMALLOC) to track packets
    dropped due to memory pressure. In production environments, we've observed
    memory exhaustion reported by memory layer stack traces, but these drops
    were not properly tracked in the SKB drop reason infrastructure.

    While most network code paths now properly report pfmemalloc drops, some
    protocol-specific socket implementations still use sk_filter() without
    drop reason tracking:
    - Bluetooth L2CAP sockets
    - CAIF sockets
    - IUCV sockets
    - Netlink sockets
    - SCTP sockets
    - Unix domain sockets

    These remaining cases represent less common paths and could be converted
    in a follow-up patch if needed. The current implementation provides
    significantly improved observability into memory pressure events in the
    network stack, especially for key protocols like TCP and UDP, helping to
    diagnose problems in production environments.

    Reported-by: Matt Fleming <mfleming@cloudflare.com>
    Signed-off-by: Jesper Dangaard Brouer <hawk@kernel.org>
    Link: https://patch.msgid.link/175268316579.2407873.11634752355644843509.stgit@firesoul
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

Signed-off-by: Antoine Tenart <atenart@redhat.com>
2026-01-23 10:03:07 +01:00
..