Page MenuHomeFreeBSD

aio_fsync_vnode: handle ERELOOKUP after VOP_FSYNC()
ClosedPublic

Authored by kib on Sep 20 2021, 9:36 AM.
Tags
None
Referenced Files
F151129778: D32023.id95398.diff
Mon, Apr 6, 7:05 AM
Unknown Object (File)
Sat, Apr 4, 7:49 PM
Unknown Object (File)
Thu, Mar 12, 4:05 PM
Unknown Object (File)
Thu, Mar 12, 3:59 AM
Unknown Object (File)
Wed, Mar 11, 9:15 PM
Unknown Object (File)
Mar 2 2026, 9:00 PM
Unknown Object (File)
Feb 28 2026, 9:01 AM
Unknown Object (File)
Feb 23 2026, 7:42 PM
Subscribers
None

Diff Detail

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

Event Timeline

kib requested review of this revision.Sep 20 2021, 9:36 AM
kib created this revision.

LGTM. I tried it with my aio_fsync/aio_waitcomplete-heavy workload and saw no problem (though that isn't saying much, as I've only ever seen ERELOOKUP/panic twice).

This revision is now accepted and ready to land.Sep 20 2021, 11:55 AM