Page MenuHomeFreeBSD

sound: Do not check for NULL if sbuf is allocated with SBUF_AUTOEXTEND
ClosedPublic

Authored by christos on Sep 29 2024, 2:09 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Aug 10, 11:37 AM
Unknown Object (File)
Mon, Aug 10, 8:38 AM
Unknown Object (File)
Sat, Aug 8, 10:27 PM
Unknown Object (File)
Sat, Aug 8, 9:14 PM
Unknown Object (File)
Sat, Aug 8, 9:33 AM
Unknown Object (File)
Sat, Aug 8, 5:57 AM
Unknown Object (File)
Sat, Aug 8, 3:33 AM
Unknown Object (File)
Fri, Aug 7, 2:06 PM
Subscribers

Diff Detail

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

Event Timeline

This revision is now accepted and ready to land.Sep 29 2024, 4:43 PM

Should we clarify this case in sbuf(9), either with the SBUF_AUTOEXTEND description or in the RETURN VALUES section for sbuf_new?

Across the tree there's a mix of checking for NULL with SBUF_AUTOEXTEND and not checking, sometimes both cases in the same file (sys/dev/acpica/acpi.c).