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)
Wed, Aug 19, 10:30 PM
Unknown Object (File)
Sat, Aug 15, 5:08 AM
Unknown Object (File)
Fri, Aug 14, 4:28 PM
Unknown Object (File)
Wed, Aug 12, 7:52 PM
Unknown Object (File)
Wed, Aug 12, 7:11 PM
Unknown Object (File)
Sat, Aug 8, 7:05 PM
Unknown Object (File)
Sat, Aug 8, 7:04 PM
Unknown Object (File)
Thu, Aug 6, 9:32 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