Fix locking for some RACK specific socket options
ClosedPublic
Actions

Authored by tuexen on Sep 27 2019, 7:45 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Nov 28 2025, 12:53 AM

	Unknown Object (File)
	Nov 22 2025, 10:44 PM

	Unknown Object (File)
	Nov 19 2025, 2:44 PM

	Unknown Object (File)
	Nov 17 2025, 8:31 PM

	Unknown Object (File)
	Nov 15 2025, 4:10 AM

	Unknown Object (File)
	Nov 14 2025, 6:34 PM

	Unknown Object (File)
	Nov 14 2025, 11:07 AM

	Unknown Object (File)
	Nov 13 2025, 11:36 PM

View All 73 Files

Subscribers

imp

Details

Reviewers

rrs

Group Reviewers

transport

Commits

rS352842: Ensure that the INP lock is released before leaving [gs]etsockopt()

Summary

Ensure that the INP lock is released before leaving [gs]etsockopt() for RACK specific socket options.

These issues were found by a syzkaller instance.

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

tuexen created this revision.Sep 27 2019, 7:45 PM

Herald added a reviewer: transport. · View Herald TranscriptSep 27 2019, 7:45 PM

Herald added a subscriber: imp. · View Herald Transcript

Harbormaster completed remote builds in B26743: Diff 62665.Sep 27 2019, 7:45 PM

rrs accepted this revision.Sep 28 2019, 9:21 AM

This revision is now accepted and ready to land.Sep 28 2019, 9:21 AM

Closed by commit rS352842: Ensure that the INP lock is released before leaving [gs]etsockopt() (authored by tuexen). · Explain WhySep 28 2019, 1:05 PM

This revision was automatically updated to reflect the committed changes.

tuexen added a commit: rS352842: Ensure that the INP lock is released before leaving [gs]etsockopt().

Revision Contents
Changeset List

Path

Size

head/

sys/

netinet/

tcp_stacks/

rack.c

13 lines

Diff 62684

View Options

head/sys/netinet/tcp_stacks/rack.c

Fix locking for some RACK specific socket optionsClosedPublicActions