[Bug 236329] [FUSE] panic when opening a file with O_EXEC

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Mar 6 18:01:09 UTC 2019


            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 at FreeBSD.org
          Reporter: asomers at 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 = 3
time = 1551894988
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0030ca4510
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 = 0x8005bc40a, rsp =
0x7fffffffe588, rbp = 0x7fffffffe600 ---

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

More information about the freebsd-bugs mailing list