Bug #8560

Reference leak on ipsec_action_t

Added by Dan McDonald 4 months ago.

Status:NewStart date:2017-08-04
Priority:LowDue date:
Assignee:-% Done:

0%

Category:networking
Target version:-
Difficulty:Medium Tags:needs-triage

Description

While verifying #8554, I found one last leaked object. It has a reference count of 1214.

> ffffff0da4a718a8::print ipsec_action_t
{
    ipa_hash = {
        hash_next = 0
        hash_pp = 0xffffff0db9ed1018
    }
    ipa_next = 0
    ipa_refs = 0x4be
    ipa_act = {
        ipa_type = 0x1
        ipa_log = 0
        ipa_u = {
            ipau_apply = {
                ipp_use_ah = 0
                ipp_use_esp = 0x1
                ipp_use_se = 0
                ipp_use_unique = 0
                ipp_use_espa = 0x1
                ipp_pad = 0
                ipp_auth_alg = 0
                ipp_encr_alg = 0xc
                ipp_esp_auth_alg = 0x7
                ipp_ah_minbits = 0
                ipp_ah_maxbits = 0
                ipp_espe_minbits = 0x80
                ipp_espe_maxbits = 0x100
                ipp_espa_minbits = 0x200
                ipp_espa_maxbits = 0x200
                ipp_km_proto = 0
                ipp_km_cookie = 0
                ipp_replay_depth = 0
            }
            ipau_reject_type = 0x12
            ipau_resolve_id = 0x12
            ipau_log_type = 0x12
        }
    }
    ipa_hval = 0xfe
    ipa_allow_clear = 0
    ipa_want_ah = 0
    ipa_want_esp = 0x1
    ipa_want_se = 0
    ipa_want_unique = 0
    ipa_pad = 0x5d6ee
    ipa_ovhd = 0x4e
}
> 

It's one action, and it appears to be (like #8554) only an issue on IPsec-using netstacks that shut down.

Also available in: Atom