diff options
| author | Poul-Henning Kamp <phk@FreeBSD.org> | 2025-10-24 07:19:31 +0000 |
|---|---|---|
| committer | Poul-Henning Kamp <phk@FreeBSD.org> | 2025-10-24 07:19:31 +0000 |
| commit | 2612f1b8649bb4f069a6a064ed714daa5f10d037 (patch) | |
| tree | 4160b7740c34839da4b505279a2c07d28ab38b27 /tests/sys/kern | |
| parent | 35f375549c7f4d479ba1d9fcd0a368b0219c4ae6 (diff) | |
One some systems, under some conditions, pulling a USB stick would
read(2) returning EIO and not ENXIO, like it should and used to.
Recoverdisk(1), which does not give up on EIO, like most programs
would, spins furiously.
Arguably, deadfs was always wrong in returning EIO, because once you
get to deadfs no operation will ever work again, but we used to
take a different path through devfs_vnops.c which got us the ENXIO.
Something changed recently, and while testing this fix, I noticed
that drm-kmod-66/i915kms may be the condition which trigger
the different code-path.
MFC to: stable/15
Fixes: 289785
Thanks to: imp, kib
Diffstat (limited to 'tests/sys/kern')
0 files changed, 0 insertions, 0 deletions
