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
F147589491: D32023.id.diff
Thu, Mar 12, 3:59 AM
F147556002: D32023.id.diff
Wed, Mar 11, 9:15 PM
Unknown Object (File)
Mon, Mar 2, 9:00 PM
Unknown Object (File)
Sat, Feb 28, 9:01 AM
Unknown Object (File)
Mon, Feb 23, 7:42 PM
Unknown Object (File)
Sun, Feb 22, 2:07 AM
Unknown Object (File)
Sun, Feb 22, 2:07 AM
Unknown Object (File)
Sun, Feb 22, 2:07 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