Page MenuHomeFreeBSD

disambiguate msleep KASSERT diagnostics
ClosedPublic

Authored by emaste on Nov 21 2016, 3:32 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, May 5, 5:58 AM
Unknown Object (File)
Feb 17 2024, 8:34 AM
Unknown Object (File)
Feb 14 2024, 7:10 PM
Unknown Object (File)
Feb 7 2024, 9:15 AM
Unknown Object (File)
Dec 28 2023, 3:12 AM
Unknown Object (File)
Dec 27 2023, 5:39 PM
Unknown Object (File)
Dec 27 2023, 5:11 PM
Unknown Object (File)
Dec 22 2023, 9:58 PM
Subscribers

Details

Summary

I encountered "panic: msleep" while investigating an issue, which led to @kib's change in D8421. I applied the change here locally while investigating, because four different cases would result in the same panic string. There may be a better way to disambiguate these cases though; what do you think?

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

emaste retitled this revision from to disambiguate msleep KASSERT diagnostics.
emaste updated this object.
emaste edited the test plan for this revision. (Show Details)
emaste added reviewers: kib, jhb.
emaste added a subscriber: kib.
kib edited edge metadata.
kib added inline comments.
sys/kern/kern_synch.c
155 ↗(On Diff #22407)

What about this line ? Although I think that we cannot really get this asserted even for extremely broken kernels.

157 ↗(On Diff #22407)

Might be say 'current thread is not running' instead of td.

This revision is now accepted and ready to land.Nov 21 2016, 3:42 PM
jhb edited edge metadata.
jhb added inline comments.
sys/kern/kern_synch.c
155 ↗(On Diff #22407)

Yeah, that is old (in 4.x p was NULL in the idle loop, but that was also all in assembly). It can probably go away. As bde@ would point out it will panic shortly anyway via a trap when td is dereferenced.

157 ↗(On Diff #22407)

Or "curthread not running". I think the existing message is ok as well.

This revision was automatically updated to reflect the committed changes.