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)
Tue, Jun 10, 7:50 AM
Unknown Object (File)
Tue, May 27, 8:14 PM
Unknown Object (File)
Wed, May 21, 11:51 PM
Unknown Object (File)
Apr 13 2025, 11:29 PM
Unknown Object (File)
Apr 12 2025, 5:53 PM
Unknown Object (File)
Apr 12 2025, 12:23 AM
Unknown Object (File)
Mar 10 2025, 3:32 AM
Unknown Object (File)
Feb 26 2025, 4:56 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