[Bug 238565] panic: vinvalbuf: dirty bufs during unmount if clustered writes return errors

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238565

--- Comment #16 from commit-hook@FreeBSD.org ---
A commit in branch stable/12 references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=7dcb5db451b66aa277bd59c61c18a5053c658915

commit 7dcb5db451b66aa277bd59c61c18a5053c658915
Author:     Konstantin Belousov <kib@FreeBSD.org>
AuthorDate: 2021-05-30 16:52:42 +0000
Commit:     Alan Somers <asomers@FreeBSD.org>
CommitDate: 2021-10-07 19:34:19 +0000

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

    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
    Reviewed by:    asomers, mckusick
    Sponsored by:   The FreeBSD Foundation
    Differential revision:  https://reviews.freebsd.org/D30555

    (cherry picked from commit 27006229f7a40a18a61a0e8fd270bc583326b690)

    fusefs: reenable the WriteCluster.cluster_write_err test

    The underlying panic was just fixed by
    revision 27006229f7a40a18a61a0e8fd270bc583326b690

    PR:             238565
    (cherry picked from commit 425bbe9e64f7af6bdb30a099bd90a32885de1ab8)

 sys/kern/vfs_subr.c          | 10 ++++------
 tests/sys/fs/fusefs/write.cc |  4 ++--
 2 files changed, 6 insertions(+), 8 deletions(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.