Differential D54088

ip6: Add explicit lock order information to catch boot-time LOR
ClosedPublic
Actions

Authored by jtl on Dec 5 2025, 5:29 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Wed, Jun 17, 9:31 PM

	Unknown Object (File)
	Wed, Jun 10, 7:41 AM

	Unknown Object (File)
	May 18 2026, 12:44 PM

	Unknown Object (File)
	May 15 2026, 5:10 PM

	Unknown Object (File)
	May 14 2026, 11:38 AM

	Unknown Object (File)
	May 14 2026, 9:06 AM

	Unknown Object (File)
	May 13 2026, 11:46 PM

	Unknown Object (File)
	May 13 2026, 7:24 PM

View All 39 Files

Subscribers

Details

Reviewers

glebius
markj
bz

Group Reviewers

transport
network

Commits

rG3f10e5985044: ip6: Add explicit lock order information to catch LOR

Summary

Over the past several years, we have had sporadic reports of a boot-time LOR between the tcphash lock and the in6_ifaddr_lock. These seems to be hard to reproduce reliably, and the WITNESS backtrace points to code which uses the correct locking order.

Adding the lock order explicitly should help us detect the call stack which uses the incorrect locking order.

Diff Detail

Repository

rG FreeBSD src repository

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

jtl created this revision.Dec 5 2025, 5:29 PM

Herald added subscribers: olce, imp. · View Herald TranscriptDec 5 2025, 5:29 PM

jtl requested review of this revision.Dec 5 2025, 5:29 PM

glebius accepted this revision as: glebius.Dec 5 2025, 5:35 PM

This revision is now accepted and ready to land.Dec 5 2025, 5:35 PM

Just FYI, at least my nightly incarnation wasn't "boot-time".

Closed by commit rG3f10e5985044: ip6: Add explicit lock order information to catch LOR (authored by jtl). · Explain WhyDec 6 2025, 7:59 PM

This revision was automatically updated to reflect the committed changes.

jtl added a commit: rG3f10e5985044: ip6: Add explicit lock order information to catch LOR.

Revision Contents
Changeset List

Path

Size

sys/

kern/

6 lines

Diff 167653

sys/kern/subr_witness.c

Loading...