Page MenuHomeFreeBSD

realtimer_expire: avoid proc lock recursion when called from itimer_proc_continue()
ClosedPublic

Authored by kib on Apr 13 2021, 1:52 PM.
Tags
None
Referenced Files
F103187170: D29746.diff
Fri, Nov 22, 1:09 AM
Unknown Object (File)
Wed, Nov 13, 10:32 PM
Unknown Object (File)
Wed, Nov 13, 10:27 PM
Unknown Object (File)
Mon, Nov 4, 10:46 AM
Unknown Object (File)
Sat, Nov 2, 7:49 AM
Unknown Object (File)
Oct 19 2024, 12:57 AM
Unknown Object (File)
Sep 29 2024, 3:15 PM
Unknown Object (File)
Sep 28 2024, 2:51 AM
Subscribers
None

Details

Summary

It is fine to drop the process lock there, process cannot exit until its timers are cleared.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kib requested review of this revision.Apr 13 2021, 1:52 PM
kib created this revision.

Upload the correct version of the patch.
PHOLD() there is not needed and is even wrong.

I believe there is a similar recursion with kqueue timers: kqtimer_proc_continue() holds the proc lock, and filt_timerexpire() may attempt to acquire it.

Handle recursion in filter_timerexpire()

This revision is now accepted and ready to land.Apr 13 2021, 8:41 PM