[Bug 296237] sys/fs/fusefs/destroy test intermittently failing in CI on riscv64

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

--- Comment #2 from commit-hook@FreeBSD.org ---
A commit in branch main references this bug:

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

commit b7d2f7c1a68c270ae5f46b8cfcfb85aa792b6b12
Author:     Alan Somers <asomers@FreeBSD.org>
AuthorDate: 2026-06-23 20:42:25 +0000
Commit:     Alan Somers <asomers@FreeBSD.org>
CommitDate: 2026-06-23 23:31:44 +0000

    fusefs: fix two intermittency bugs in the destroy tests

    * Though undocumented, statfs(2) can sometimes return EBADF or ENOENT
      while an unmount is in progress.

    * In MockFS::write_response, write(2) may fail if m_fuse_fd has already
      been closed.  This doesn't happen in the normal sequence of events,
      but it can happen if some process unrelated to the test nosily decides
      to access the test file system while it's being unmounted.

    PR:             296237
    Reported by:    siva
    MFC after:      2 weeks
    Sponsored by:   ConnectWise
    Reviewed by:    siva
    Differential Revision: https://reviews.freebsd.org/D57787

 tests/sys/fs/fusefs/destroy.cc | 16 +++++++++++++++-
 tests/sys/fs/fusefs/mockfs.cc  |  2 ++
 2 files changed, 17 insertions(+), 1 deletion(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.