Date: Tue, 05 Mar 2019 00:24:38 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 236236] [FUSE] support FUSE_MKNOD Message-ID: <bug-236236-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236236 Bug ID: 236236 Summary: [FUSE] support FUSE_MKNOD Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: asomers@FreeBSD.org Nascent FUSE_MKNOD support was removed in r239925 because of a bug in the f= use fifo code. But FUSE_MKNOD is important for more than just fifos. We should reenable support for the following reasons: * To create chr device nodes, especially for preparing bootable media * To create blk device nodes, especially for preparing bootable Linux media= or for copying bootable Linux media. * As a fallback for fuse filesystems that don't support FUSE_CREATE. The F= USE protocol requires the kernel to fall back to FUSE_MKNOD/FUSE_OPEN if a=20 filesystem returns ENOSYS for FUSE_CREATE. * Hey, fifos are useful too, right? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236236-227>