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)
Mon, Nov 17, 3:07 AM
Unknown Object (File)
Mon, Nov 17, 1:26 AM
Unknown Object (File)
Mon, Nov 17, 1:26 AM
Unknown Object (File)
Mon, Nov 17, 1:26 AM
Unknown Object (File)
Sun, Nov 16, 11:29 PM
Unknown Object (File)
Thu, Nov 13, 7:05 PM
Unknown Object (File)
Nov 3 2025, 2:09 PM
Unknown Object (File)
Oct 30 2025, 5:08 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