/freebsd/lib/libsys/ |
H A D | chmod.2 | diff bfd03046d18776ea70785ca1ef36dfc60822de3b Sun Nov 03 15:39:32 CET 2024 Mark Johnston <markj@FreeBSD.org> unix: Add support for atomically setting the socket mode
With this patch, it is possible to call fchmod() on a unix socket prior to binding it to the filesystem namespace, so that the mode is set atomically. Without this, one has to call chmod() after bind(), leaving a window where threads can connect to the socket with the default mode. After bind(), fchmod() reverts to failing with EINVAL.
This interface is copied from Linux.
The behaviour of fstat() is unmodified, i.e., it continues to return the mode as set by soo_stat().
PR: 282393 Reviewed by: kib MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D47361
|
/freebsd/tests/sys/kern/ |
H A D | unix_dgram.c | diff bfd03046d18776ea70785ca1ef36dfc60822de3b Sun Nov 03 15:39:32 CET 2024 Mark Johnston <markj@FreeBSD.org> unix: Add support for atomically setting the socket mode
With this patch, it is possible to call fchmod() on a unix socket prior to binding it to the filesystem namespace, so that the mode is set atomically. Without this, one has to call chmod() after bind(), leaving a window where threads can connect to the socket with the default mode. After bind(), fchmod() reverts to failing with EINVAL.
This interface is copied from Linux.
The behaviour of fstat() is unmodified, i.e., it continues to return the mode as set by soo_stat().
PR: 282393 Reviewed by: kib MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D47361
|
/freebsd/share/man/man4/ |
H A D | unix.4 | diff bfd03046d18776ea70785ca1ef36dfc60822de3b Sun Nov 03 15:39:32 CET 2024 Mark Johnston <markj@FreeBSD.org> unix: Add support for atomically setting the socket mode
With this patch, it is possible to call fchmod() on a unix socket prior to binding it to the filesystem namespace, so that the mode is set atomically. Without this, one has to call chmod() after bind(), leaving a window where threads can connect to the socket with the default mode. After bind(), fchmod() reverts to failing with EINVAL.
This interface is copied from Linux.
The behaviour of fstat() is unmodified, i.e., it continues to return the mode as set by soo_stat().
PR: 282393 Reviewed by: kib MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D47361
|
/freebsd/sys/sys/ |
H A D | unpcb.h | diff bfd03046d18776ea70785ca1ef36dfc60822de3b Sun Nov 03 15:39:32 CET 2024 Mark Johnston <markj@FreeBSD.org> unix: Add support for atomically setting the socket mode
With this patch, it is possible to call fchmod() on a unix socket prior to binding it to the filesystem namespace, so that the mode is set atomically. Without this, one has to call chmod() after bind(), leaving a window where threads can connect to the socket with the default mode. After bind(), fchmod() reverts to failing with EINVAL.
This interface is copied from Linux.
The behaviour of fstat() is unmodified, i.e., it continues to return the mode as set by soo_stat().
PR: 282393 Reviewed by: kib MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D47361
|
H A D | protosw.h | diff bfd03046d18776ea70785ca1ef36dfc60822de3b Sun Nov 03 15:39:32 CET 2024 Mark Johnston <markj@FreeBSD.org> unix: Add support for atomically setting the socket mode
With this patch, it is possible to call fchmod() on a unix socket prior to binding it to the filesystem namespace, so that the mode is set atomically. Without this, one has to call chmod() after bind(), leaving a window where threads can connect to the socket with the default mode. After bind(), fchmod() reverts to failing with EINVAL.
This interface is copied from Linux.
The behaviour of fstat() is unmodified, i.e., it continues to return the mode as set by soo_stat().
PR: 282393 Reviewed by: kib MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D47361
|
/freebsd/sys/kern/ |
H A D | sys_socket.c | diff bfd03046d18776ea70785ca1ef36dfc60822de3b Sun Nov 03 15:39:32 CET 2024 Mark Johnston <markj@FreeBSD.org> unix: Add support for atomically setting the socket mode
With this patch, it is possible to call fchmod() on a unix socket prior to binding it to the filesystem namespace, so that the mode is set atomically. Without this, one has to call chmod() after bind(), leaving a window where threads can connect to the socket with the default mode. After bind(), fchmod() reverts to failing with EINVAL.
This interface is copied from Linux.
The behaviour of fstat() is unmodified, i.e., it continues to return the mode as set by soo_stat().
PR: 282393 Reviewed by: kib MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D47361
|
H A D | uipc_usrreq.c | diff bfd03046d18776ea70785ca1ef36dfc60822de3b Sun Nov 03 15:39:32 CET 2024 Mark Johnston <markj@FreeBSD.org> unix: Add support for atomically setting the socket mode
With this patch, it is possible to call fchmod() on a unix socket prior to binding it to the filesystem namespace, so that the mode is set atomically. Without this, one has to call chmod() after bind(), leaving a window where threads can connect to the socket with the default mode. After bind(), fchmod() reverts to failing with EINVAL.
This interface is copied from Linux.
The behaviour of fstat() is unmodified, i.e., it continues to return the mode as set by soo_stat().
PR: 282393 Reviewed by: kib MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D47361
|