Page MenuHomeFreeBSD

malloc: Fix domainset usage in malloc_domainset() for large allocs
ClosedPublic

Authored by markj on Jul 17 2026, 9:13 PM.
Tags
None
Referenced Files
F171134126: D58316.id.diff
Tue, Sep 8, 10:17 PM
F171099521: D58316.id183153.diff
Tue, Sep 8, 4:59 PM
F171094174: D58316.diff
Tue, Sep 8, 4:16 PM
F171093859: D58316.diff
Tue, Sep 8, 4:13 PM
F171022576: D58316.diff
Tue, Sep 8, 6:09 AM
Unknown Object (File)
Sun, Sep 6, 9:00 AM
Unknown Object (File)
Wed, Sep 2, 2:19 PM
Unknown Object (File)
Wed, Sep 2, 2:05 PM
Subscribers

Details

Summary

We should of course pass the provided domainset rather than copying what
plain malloc() does.

Fixes: 89deca0a3361 ("malloc: make malloc_large closer to standalone")

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Maybe one day we should plumb it for malloc_dbg / memguard_alloc too.

This revision is now accepted and ready to land.Jul 17 2026, 9:22 PM

Maybe one day we should plumb it for malloc_dbg / memguard_alloc too.

Do you use memguard at all? I haven't needed to reach for it since KASAN was added.

Maybe one day we should plumb it for malloc_dbg / memguard_alloc too.

Do you use memguard at all? I haven't needed to reach for it since KASAN was added.

Yes, though maybe there's a better way to do what we're doing. memguard can be used with only small performance impact for types/zones that don't match vm.memguard.desc. Actually I was recently thinking about a way to use memguard more broadly for infrequent allocations.