Skip to content

The memory of AUSF ausfContext keeps growing as more users connect #62

Description

@mabo-zt

I noticed something suspicious in the AUSF implementation, but I'm not sure if it's actually a bug

a) global variable

var ausfContext AUSFContext  // global variable

b) There are add functions, but no delete functions.

// Add
func AddAusfUeContextToPool(ausfUeContext *AusfUeContext) {
    ausfContext.UePool.Store(ausfUeContext.Supi, ausfUeContext)
}

func AddSuciSupiPairToMap(supiOrSuci string, supi string) {
    ausfContext.suciSupiMap.Store(supiOrSuci, newPair)
}

// there is no delete functions, such as:
// func DeleteAusfUeContextFromPool(supi string) { ... }
// func DeleteSuciSupiPairFromMap(supiOrSuci string) { ... }

With a massive number of users, this would lead to unbounded memory growth.
Is this a case of human resource constraints, or is there actually no need for this method?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions