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)
Sat, Oct 18, 5:34 PM
Unknown Object (File)
Thu, Oct 16, 2:51 AM
Unknown Object (File)
Sep 18 2025, 5:21 PM
Unknown Object (File)
Sep 4 2025, 3:38 PM
Unknown Object (File)
Sep 4 2025, 1:43 AM
Unknown Object (File)
Aug 30 2025, 1:49 PM
Unknown Object (File)
Aug 25 2025, 9:15 AM
Unknown Object (File)
Aug 24 2025, 11:12 PM
Subscribers
None

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped

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