Date: Thu, 14 Jan 2021 16:04:15 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 252673] Read on a SEQPACKET AF_UNIX socket returns the wrong error when disallowed by Capsicum Message-ID: <bug-252673-227-N6tl3J0bb1@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-252673-227@https.bugs.freebsd.org/bugzilla/> References: <bug-252673-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252673 --- Comment #2 from David Chisnall <theraven@FreeBSD.org> --- Curious. That test also passes for me. I'll see if I can produce a reduced test case. In the program where I encountered this, the fd is actually `du= p`'d and then passed to a child process (`vfork` + `execve`) and is actually cal= ling `__sys_read` not `read`, because the first `read` is before enough libc is = set up for `read` to not SEGV. I've added a `dup` and a `fork` to your test an= d it still does the right thing. Is there anything in the file descriptor inheritance logic across `execve` that may cause a change here? --=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-252673-227-N6tl3J0bb1>