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)
Thu, May 14, 12:32 PM
Unknown Object (File)
Thu, May 14, 10:41 AM
Unknown Object (File)
Thu, May 14, 4:44 AM
Unknown Object (File)
Wed, May 13, 2:00 AM
Unknown Object (File)
Mon, May 11, 3:49 PM
Unknown Object (File)
Fri, May 1, 8:03 PM
Unknown Object (File)
Thu, Apr 23, 3:12 AM
Unknown Object (File)
Wed, Apr 22, 11:52 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