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
F162944150: D32023.id95382.diff
Sat, Jul 18, 1:49 PM
F162939838: D32023.diff
Sat, Jul 18, 12:42 PM
Unknown Object (File)
Fri, Jul 3, 12:52 AM
Unknown Object (File)
Thu, Jul 2, 10:43 PM
Unknown Object (File)
Thu, Jul 2, 8:38 PM
Unknown Object (File)
Wed, Jul 1, 3:20 AM
Unknown Object (File)
May 14 2026, 12:32 PM
Unknown Object (File)
May 14 2026, 10:41 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