Bug 216922 - bpf(4): opening already opened device returns EBUSY; not documented as supported error in open(2) and not documented in bpf manpages
Summary: bpf(4): opening already opened device returns EBUSY; not documented as suppor...
Status: New
Alias: None
Product: Documentation
Classification: Unclassified
Component: Manual Pages (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-doc (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-08 18:13 UTC by Enji Cooper
Modified: 2018-08-05 06:05 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Enji Cooper freebsd_committer freebsd_triage 2017-02-08 18:13:38 UTC 
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)?).