Date: Wed, 08 Feb 2017 18:13:38 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 216922] bpf(4): opening already opened device returns EBUSY; not documented as supported error in open(2) Message-ID: <bug-216922-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216922 Bug ID: 216922 Summary: bpf(4): opening already opened device returns EBUSY; not documented as supported error in open(2) Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: ngie@FreeBSD.org We have some code at $work that opens bpf(4) devices. It has to handle EBUSY because of this line of code: https://svnweb.freebsd.org/base/head/sys/net/bpf.c?annotate=3D303382#l869 It seems like there are 2 bugs, potentially: - open(2) should note that behavior for character devices may vary from the ERRORS section. - bpf(4) returning EBUSY when the device is in use should be documented, somewhere (maybe in bpf(9)?). --=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-216922-8>