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
Unknown Object (File)
Fri, Aug 8, 6:10 AM
Unknown Object (File)
Wed, Aug 6, 12:04 AM
Unknown Object (File)
Fri, Aug 1, 10:46 PM
Unknown Object (File)
Thu, Jul 24, 11:45 AM
Unknown Object (File)
Jul 7 2025, 2:58 AM
Unknown Object (File)
Jul 2 2025, 7:36 PM
Unknown Object (File)
Jun 29 2025, 6:58 PM
Unknown Object (File)
Jun 27 2025, 11:11 AM
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