Date: Wed, 06 Mar 2019 18:01:06 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 236329] [FUSE] panic when opening a file with O_EXEC Message-ID: <bug-236329-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236329 Bug ID: 236329 Summary: [FUSE] panic when opening a file with O_EXEC 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 Simply opening a fuse-backed file with open(pathname, O_EXEC) is enough to trigger a panic. The bug is in fuse_filehandle_xlate_from_fflags, which assumes that at least one of FREAD or FWRITE will always be set. But that's not true when opening a file with O_EXEC. It seems surprising that nobody's run into this bug already. panic: FUSE: What kind of a flag is this (40000)? cpuid =3D 3 time =3D 1551894988 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0030ca4= 510 vpanic() at vpanic+0x1b4/frame 0xfffffe0030ca4570 panic() at panic+0x43/frame 0xfffffe0030ca45d0 fuse_vnop_open() at fuse_vnop_open+0xdf/frame 0xfffffe0030ca4610 VOP_OPEN_APV() at VOP_OPEN_APV+0x60/frame 0xfffffe0030ca4630 vn_open_vnode() at vn_open_vnode+0x1b1/frame 0xfffffe0030ca46d0 vn_open_cred() at vn_open_cred+0x34c/frame 0xfffffe0030ca4820 kern_openat() at kern_openat+0x1fd/frame 0xfffffe0030ca4990 amd64_syscall() at amd64_syscall+0x276/frame 0xfffffe0030ca4ab0 fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe0030ca4ab0 --- syscall (499, FreeBSD ELF64, sys_openat), rip =3D 0x8005bc40a, rsp =3D 0x7fffffffe588, rbp =3D 0x7fffffffe600 --- --=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-236329-227>