inpcb: a pcb may travel only from the wild hash to exact, not vice versa
ClosedPublic
Actions

Authored by glebius on May 26 2026, 4:06 AM.

Tags

None

Referenced Files

	Unknown Object (File)
	Wed, Sep 16, 12:11 AM

	Unknown Object (File)
	Sun, Sep 13, 10:04 AM

	Unknown Object (File)
	Thu, Sep 10, 8:58 PM

	Unknown Object (File)
	Thu, Sep 10, 5:02 AM

	Unknown Object (File)
	Tue, Sep 8, 9:40 PM

	Unknown Object (File)
	Tue, Sep 8, 2:15 PM

	Unknown Object (File)
	Sat, Sep 5, 12:51 AM

	Unknown Object (File)
	Fri, Sep 4, 1:24 PM

View All 62 Files

Subscribers

imp

melifaro

Details

Reviewers

markj

Group Reviewers

network

Commits

rGca91300c0749: inpcb: a pcb may travel only from the wild hash to exact, not vice versa

Summary

The only possible way to exercise in_pcbrehash() is to bind(2) and then
connect(2). The second branch was a dead code since fdb987bebddf.

Diff Detail

Repository

rG FreeBSD src repository

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

glebius created this revision.May 26 2026, 4:06 AM

Herald added subscribers: melifaro, imp. · View Herald TranscriptMay 26 2026, 4:06 AM

glebius requested review of this revision.May 26 2026, 4:06 AM

Harbormaster completed remote builds in B73439: Diff 178590.May 26 2026, 4:06 AM

markj accepted this revision.May 26 2026, 2:15 PM

This revision is now accepted and ready to land.May 26 2026, 2:15 PM

Closed by commit rGca91300c0749: inpcb: a pcb may travel only from the wild hash to exact, not vice versa (authored by glebius). · Explain WhyMay 28 2026, 5:07 AM

This revision was automatically updated to reflect the committed changes.

glebius added a commit: rGca91300c0749: inpcb: a pcb may travel only from the wild hash to exact, not vice versa.

Revision Contents
Changeset List

Path

Size

sys/

netinet/

in_pcb.c

23 lines

Diff 178777

View Options

inpcb: a pcb may travel only from the wild hash to exact, not vice versaClosedPublicActions