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, Apr 13, 7:58 AM
Unknown Object (File)
Mar 19 2024, 4:22 AM
Unknown Object (File)
Mar 19 2024, 2:52 AM
Unknown Object (File)
Mar 7 2024, 4:46 PM
Unknown Object (File)
Jan 9 2024, 2:18 AM
Unknown Object (File)
Dec 23 2023, 11:13 AM
Unknown Object (File)
Dec 14 2023, 8:34 PM
Unknown Object (File)
Sep 10 2023, 1:21 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