Page MenuHomeFreeBSD

vinvalbuf: do not panic if we were unable to flush dirty buffers
ClosedPublic

Authored by kib on May 30 2021, 5:13 PM.
Tags
None
Referenced Files
F159102325: D30555.diff
Wed, Jun 10, 3:48 AM
Unknown Object (File)
Tue, May 19, 5:46 AM
Unknown Object (File)
Tue, May 19, 5:46 AM
Unknown Object (File)
Mon, May 18, 2:32 PM
Unknown Object (File)
Mon, May 18, 2:32 PM
Unknown Object (File)
Mon, May 18, 2:32 PM
Unknown Object (File)
Mon, May 18, 2:32 PM
Unknown Object (File)
Sun, May 17, 9:49 PM
Subscribers

Details

Summary

Return EBUSY instead and let caller to handle the issue.

For vgone()/vnode reclamation, caller first does vinvalbuf(V_SAVE), which return EBUSY in case dirty buffers where not flushed. Then caller calls vinvalbuf(0) due to non-zero return, which gets rid of all dirty buffers without dependencies.

PR: 238565

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kib requested review of this revision.May 30 2021, 5:13 PM
kib created this revision.

Works for me. You should also reenable the test in tests/sys/fs/fusefs/write.cc.

This revision is now accepted and ready to land.May 30 2021, 6:35 PM

You should also reenable the test in tests/sys/fs/fusefs/write.cc.

Please do it yourself after my change.