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
Unknown Object (File)
Tue, Sep 8, 8:43 PM
Unknown Object (File)
Tue, Sep 8, 11:39 AM
Unknown Object (File)
Tue, Sep 8, 4:52 AM
Unknown Object (File)
Mon, Sep 7, 10:32 PM
Unknown Object (File)
Sat, Sep 5, 11:57 PM
Unknown Object (File)
Sat, Sep 5, 4:30 PM
Unknown Object (File)
Sat, Sep 5, 4:01 AM
Unknown Object (File)
Fri, Sep 4, 3:52 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.