https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216922
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: n...@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=303382#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)?).
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
