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, Mar 10, 3:32 AM
Unknown Object (File)
Wed, Feb 26, 4:56 PM
Unknown Object (File)
Feb 21 2025, 12:45 PM
Unknown Object (File)
Feb 18 2025, 1:33 AM
Unknown Object (File)
Feb 15 2025, 6:08 PM
Unknown Object (File)
Jan 19 2025, 11:40 AM
Unknown Object (File)
Jan 19 2025, 8:17 AM
Unknown Object (File)
Jan 9 2025, 3:57 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