Searched hist:51583 (Results 1 - 9 of 9) sorted by relevance
| /freebsd-11-stable/sys/dev/wb/ | ||
| H A D | if_wb.c | diff 51583 Thu Sep 23 01:32:57 MDT 1999 wpaul As suggested by phk, unconditionalize BPF support in these drivers. Since there are stubs compiled into the kernel if BPF support is not enabled, there aren't any problems with unresolved symbols. The modules in /modules are compiled with BPF support enabled anyway, so the most this will do is bloat GENERIC a little. |
| /freebsd-11-stable/sys/dev/tl/ | ||
| H A D | if_tl.c | diff 51583 Thu Sep 23 01:32:57 MDT 1999 wpaul As suggested by phk, unconditionalize BPF support in these drivers. Since there are stubs compiled into the kernel if BPF support is not enabled, there aren't any problems with unresolved symbols. The modules in /modules are compiled with BPF support enabled anyway, so the most this will do is bloat GENERIC a little. |
| /freebsd-11-stable/sys/dev/sf/ | ||
| H A D | if_sf.c | diff 51583 Thu Sep 23 01:32:57 MDT 1999 wpaul As suggested by phk, unconditionalize BPF support in these drivers. Since there are stubs compiled into the kernel if BPF support is not enabled, there aren't any problems with unresolved symbols. The modules in /modules are compiled with BPF support enabled anyway, so the most this will do is bloat GENERIC a little. |
| /freebsd-11-stable/sys/dev/ti/ | ||
| H A D | if_ti.c | diff 51583 Thu Sep 23 01:32:57 MDT 1999 wpaul As suggested by phk, unconditionalize BPF support in these drivers. Since there are stubs compiled into the kernel if BPF support is not enabled, there aren't any problems with unresolved symbols. The modules in /modules are compiled with BPF support enabled anyway, so the most this will do is bloat GENERIC a little. |
| /freebsd-11-stable/sys/dev/xl/ | ||
| H A D | if_xl.c | diff 51583 Thu Sep 23 01:32:57 MDT 1999 wpaul As suggested by phk, unconditionalize BPF support in these drivers. Since there are stubs compiled into the kernel if BPF support is not enabled, there aren't any problems with unresolved symbols. The modules in /modules are compiled with BPF support enabled anyway, so the most this will do is bloat GENERIC a little. |
| /freebsd-11-stable/sys/dev/rl/ | ||
| H A D | if_rl.c | diff 51583 Thu Sep 23 01:32:57 MDT 1999 wpaul As suggested by phk, unconditionalize BPF support in these drivers. Since there are stubs compiled into the kernel if BPF support is not enabled, there aren't any problems with unresolved symbols. The modules in /modules are compiled with BPF support enabled anyway, so the most this will do is bloat GENERIC a little. |
| /freebsd-11-stable/sys/kern/ | ||
| H A D | vfs_default.c | diff 232317 Wed Feb 29 19:45:48 MST 2012 trociny Introduce VOP_UNP_BIND(), VOP_UNP_CONNECT(), and VOP_UNP_DETACH() operations for setting and accessing vnode's v_socket field. The operations are necessary to implement proper unix socket handling on layered file systems like nullfs(5). This change fixes the long standing issue with nullfs(5) being in that unix sockets did not work between lower and upper layers: if we bound to a socket on the lower layer we could connect only to the lower path; if we bound to the upper layer we could connect only to the upper path. The new behavior is one can connect to both the lower and the upper paths regardless what layer path one binds to. PR: kern/51583, kern/159663 Suggested by: kib Reviewed by: arch MFC after: 2 weeks |
| H A D | uipc_usrreq.c | diff 232317 Wed Feb 29 19:45:48 MST 2012 trociny Introduce VOP_UNP_BIND(), VOP_UNP_CONNECT(), and VOP_UNP_DETACH() operations for setting and accessing vnode's v_socket field. The operations are necessary to implement proper unix socket handling on layered file systems like nullfs(5). This change fixes the long standing issue with nullfs(5) being in that unix sockets did not work between lower and upper layers: if we bound to a socket on the lower layer we could connect only to the lower path; if we bound to the upper layer we could connect only to the upper path. The new behavior is one can connect to both the lower and the upper paths regardless what layer path one binds to. PR: kern/51583, kern/159663 Suggested by: kib Reviewed by: arch MFC after: 2 weeks |
| /freebsd-11-stable/sys/sys/ | ||
| H A D | vnode.h | diff 232317 Wed Feb 29 19:45:48 MST 2012 trociny Introduce VOP_UNP_BIND(), VOP_UNP_CONNECT(), and VOP_UNP_DETACH() operations for setting and accessing vnode's v_socket field. The operations are necessary to implement proper unix socket handling on layered file systems like nullfs(5). This change fixes the long standing issue with nullfs(5) being in that unix sockets did not work between lower and upper layers: if we bound to a socket on the lower layer we could connect only to the lower path; if we bound to the upper layer we could connect only to the upper path. The new behavior is one can connect to both the lower and the upper paths regardless what layer path one binds to. PR: kern/51583, kern/159663 Suggested by: kib Reviewed by: arch MFC after: 2 weeks |
Completed in 606 milliseconds