#
369bde8f |
| 06-Dec-2024 |
riastradh <riastradh@NetBSD.org> |
sys/kern/sys_socket.c, uipc_*.c: Sprinkle SET_ERROR dtrace probes.
PR kern/58378: Kernel error code origination lacks dtrace probes
|
#
718bb391 |
| 06-Dec-2024 |
riastradh <riastradh@NetBSD.org> |
sys/kern/sys_socket.c, uipc_*.c: Nix trailing whitespace.
No functional change intended.
|
#
d54d7c75 |
| 06-Dec-2024 |
riastradh <riastradh@NetBSD.org> |
sys/kern/sys_socket.c, uipc_*.c: Sort includes.
No functional change intended.
|
#
35955797 |
| 22-Apr-2023 |
riastradh <riastradh@NetBSD.org> |
file(9): New fo_posix_fadvise operation.
XXX kernel revbump -- changes struct fileops API and ABI
|
#
b0e1b1fb |
| 22-Apr-2023 |
riastradh <riastradh@NetBSD.org> |
file(9): New fo_fpathconf operation.
XXX kernel revbump -- struct fileops API and ABI change
|
#
546702a6 |
| 17-Nov-2020 |
chs <chs@NetBSD.org> |
When SS_RESTARTSYS was added, it was accidentally given the same value as the existing SS_ASYNC. SS_ASYNC was already vestigial at that point, having been superceded by SB_ASYNC, however the SS_ASYN
When SS_RESTARTSYS was added, it was accidentally given the same value as the existing SS_ASYNC. SS_ASYNC was already vestigial at that point, having been superceded by SB_ASYNC, however the SS_ASYNC flag is still set and cleared, unlessly because it is never checked. Fix this conflict by removing SS_ASYNC and its vestigial uses.
show more ...
|
#
5047e05c |
| 04-Dec-2018 |
maya <maya@NetBSD.org> |
soo_fcntl is identical to fnullop_fcntl, use the latter
ok kamil mrg
|
#
d3646d15 |
| 01-Aug-2018 |
rjs <rjs@NetBSD.org> |
Add ioctl(2) handler for kernel part of sctp_peeloff().
|
#
ea05286d |
| 30-Nov-2017 |
christos <christos@NetBSD.org> |
add fo_name so we can identify the fileops in a simple way.
|
#
06f11aad |
| 22-Nov-2017 |
ozaki-r <ozaki-r@NetBSD.org> |
Hold KERNEL_LOCK on if_ioctl selectively based on IFEF_MPSAFE
If IFEF_MPSAFE is set, hold the lock and otherwise don't hold.
This change requires additions of KERNEL_LOCK to subsequence functions f
Hold KERNEL_LOCK on if_ioctl selectively based on IFEF_MPSAFE
If IFEF_MPSAFE is set, hold the lock and otherwise don't hold.
This change requires additions of KERNEL_LOCK to subsequence functions from if_ioctl such as ifmedia_ioctl and ifioctl_common to protect non-MP-safe components.
Proposed on tech-kern@ and tech-net@
show more ...
|
#
8bc54e5b |
| 07-Jul-2016 |
msaitoh <msaitoh@NetBSD.org> |
KNF. Remove extra spaces. No functional change.
|
#
45b1ec74 |
| 05-Sep-2014 |
matt <matt@NetBSD.org> |
Try not to use f_data, use f_{vnode,socket,pipe,mqueue,kqueue,ksem} to get a correctly typed pointer.
|
#
a60320ca |
| 06-Jul-2014 |
rtr <rtr@NetBSD.org> |
* split PRU_SENSE functionality out of xxx_usrreq() switches and place into separate xxx_stat(struct socket *, struct stat *) functions. * replace calls using pr_generic with req == PRU_SENSE with
* split PRU_SENSE functionality out of xxx_usrreq() switches and place into separate xxx_stat(struct socket *, struct stat *) functions. * replace calls using pr_generic with req == PRU_SENSE with pr_stat().
further change will follow that cleans up the pattern used to extract the pcb and test for its presence.
reviewed by rmind
show more ...
|
#
0dedd977 |
| 01-Jul-2014 |
rtr <rtr@NetBSD.org> |
fix parameter types in pr_ioctl, called xx_control() functions and remove abuse of pointer to struct mbuf type.
param2 changed to u_long type and uses parameter name 'cmd' (ioctl command) param3 cha
fix parameter types in pr_ioctl, called xx_control() functions and remove abuse of pointer to struct mbuf type.
param2 changed to u_long type and uses parameter name 'cmd' (ioctl command) param3 changed to void * type and uses parameter name 'data' param4 changed to struct ifnet * and uses parameter name 'ifp' param5 has been removed (formerly struct lwp *) and uses of 'l' have been replaced with curlwp from curproc(9).
callers have had (now unnecessary) casts to struct mbuf * removed, called code has had (now unnecessary) casts to u_long, void * and struct ifnet * respectively removed.
reviewed by rmind@
show more ...
|
#
c5cb3493 |
| 23-Jun-2014 |
rtr <rtr@NetBSD.org> |
where appropriate rename xxx_ioctl() struct mbuf * parameters from `control' to `ifp' after split from xxx_usrreq().
sys_socket.c fix wrapping of arguments to be consistent with other function c
where appropriate rename xxx_ioctl() struct mbuf * parameters from `control' to `ifp' after split from xxx_usrreq().
sys_socket.c fix wrapping of arguments to be consistent with other function calls in the file after replacing pr_usrreq() call with pr_ioctl() which required one less argument.
link_proto.c fix indentation of parameters in link_ioctl() prototype to be consistent with the rest of the file.
discussed with rmind@
show more ...
|
#
d54d7ab2 |
| 22-Jun-2014 |
rtr <rtr@NetBSD.org> |
* split PRU_CONTROL functionality out of xxx_userreq() switches and place into separate xxx_ioctl() functions. * place KASSERT(req != PRU_CONTROL) inside xxx_userreq() as it is now inappropriate
* split PRU_CONTROL functionality out of xxx_userreq() switches and place into separate xxx_ioctl() functions. * place KASSERT(req != PRU_CONTROL) inside xxx_userreq() as it is now inappropriate for req = PRU_CONTROL in xxx_userreq(). * replace calls to pr_generic() with req = PRU_CONTROL with pr_ioctl(). * remove & fixup references to PRU_CONTROL xxx_userreq() function comments. * fix various comments references for xxx_userreq() that mentioned PRU_CONTROL as xxx_userreq() no longer handles the request.
a further change will follow to fix parameter and naming inconsistencies retained from original code.
Reviewed by rmind@
show more ...
|
#
39bd8dee |
| 18-May-2014 |
rmind <rmind@NetBSD.org> |
Add struct pr_usrreqs with a pr_generic function and prepare for the dismantling of pr_usrreq in the protocols; no functional change intended. PRU_ATTACH/PRU_DETACH changes will follow soon.
Bump fo
Add struct pr_usrreqs with a pr_generic function and prepare for the dismantling of pr_usrreq in the protocols; no functional change intended. PRU_ATTACH/PRU_DETACH changes will follow soon.
Bump for struct protosw. Welcome to 6.99.62!
show more ...
|
#
0f54014c |
| 26-Apr-2014 |
pooka <pooka@NetBSD.org> |
Decouple sockets linkage from interface code by making ifioctl() a pointer.
|
#
18144432 |
| 26-Apr-2014 |
pooka <pooka@NetBSD.org> |
It's been > 20years since rtioctl() did something. Let's just remove that special way of returning EOPNOTSUPP.
|
#
87d8a6fa |
| 20-Dec-2011 |
christos <christos@NetBSD.org> |
- Eliminate so_nbio and turn it into a bit SS_NBIO in so_state. - Introduce MSG_NBIO so that we can turn non blocking i/o on a per call basis - Use MSG_NBIO to fix the XXX: multi-threaded issues on t
- Eliminate so_nbio and turn it into a bit SS_NBIO in so_state. - Introduce MSG_NBIO so that we can turn non blocking i/o on a per call basis - Use MSG_NBIO to fix the XXX: multi-threaded issues on the fifo sockets. - Don't set SO_CANTRCVMORE, if we were interrupted (perhaps do it for all errors?).
show more ...
|
#
a256291c |
| 30-Jun-2011 |
dyoung <dyoung@NetBSD.org> |
Don't cast a pointer void * before passing to memset(), that's not necessary. Use NULL instead of (type *)0. This patch produces no change in the generated assembly.
|
#
2a54322c |
| 20-Dec-2009 |
dsl <dsl@NetBSD.org> |
If a multithreaded app closes an fd while another thread is blocked in read/write/accept, then the expectation is that the blocked thread will exit and the close complete. Since only one fd is affect
If a multithreaded app closes an fd while another thread is blocked in read/write/accept, then the expectation is that the blocked thread will exit and the close complete. Since only one fd is affected, but many fd can refer to the same file, the close code can only request the fs code unblock with ERESTART. Fixed for pipes and sockets, ERESTART will only be generated after such a close - so there should be no change for other programs. Also rename fo_abort() to fo_restart() (this used to be fo_drain()). Fixes PR/26567
show more ...
|
#
7a42c833 |
| 09-Dec-2009 |
dsl <dsl@NetBSD.org> |
Rename fo_drain() to fo_abort(), 'drain' is used to mean 'wait for output do drain' in many places, whereas fo_drain() was called in order to force blocking read()/write() etc calls to return to user
Rename fo_drain() to fo_abort(), 'drain' is used to mean 'wait for output do drain' in many places, whereas fo_drain() was called in order to force blocking read()/write() etc calls to return to userspace so that a close() call from a different thread can complete. In the sockets code comment out the broken code in the inner function, it was being called from compat code.
show more ...
|
#
48320d4c |
| 08-Apr-2009 |
ad <ad@NetBSD.org> |
soo_ioctl:
- cosmetic change after merge of socket locking patch. - add a comment.
|
#
9635fa68 |
| 08-Apr-2009 |
ad <ad@NetBSD.org> |
Patch out soo_drain until I fix it to work correctly.
|