Page MenuHomeFreeBSD

tcp: Shouldn't drain empty sbuf
ClosedPublic

Authored by rscheff on Mar 31 2021, 11:01 PM.
Tags
None
Referenced Files
F154647488: D29524.id86697.diff
Wed, Apr 29, 3:21 AM
F154576637: D29524.id86697.diff
Tue, Apr 28, 11:13 PM
Unknown Object (File)
Thu, Apr 23, 12:10 AM
Unknown Object (File)
Mon, Apr 20, 7:37 AM
Unknown Object (File)
Sat, Apr 18, 6:40 PM
Unknown Object (File)
Sat, Apr 18, 9:39 AM
Unknown Object (File)
Fri, Apr 17, 10:44 AM
Unknown Object (File)
Fri, Apr 17, 9:23 AM
Subscribers

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 38251
Build 35140: arc lint + arc unit

Event Timeline

  • fix typo in assert string
sys/netinet/tcp_hostcache.c
709

Maybe add a comment why you are doing this dance. It wasn't obvious for us...

  • add comment to explain why do_drain is needed
sys/netinet/tcp_hostcache.c
711

Not sure coordination is involved. Isn't it more that one should not call sbuf_drain() with an empty buffer. Please state that and finish the sentence with a full stop (.).

This revision is now accepted and ready to land.Apr 1 2021, 2:40 PM
This revision was automatically updated to reflect the committed changes.

I would probably instead have changed sbuf_drain() to just return instead of asserting. Asserting made sense when it was a private implementation function, as a public API I think just returning instead of asserting is better behavior.