Searched hist:"28036 f44" (Results 1 – 5 of 5) sorted by relevance
/openbmc/linux/net/rxrpc/ |
H A D | security.c | 28036f44 Mon Jun 05 08:30:49 CDT 2017 David Howells <dhowells@redhat.com> rxrpc: Permit multiple service binding
Permit bind() to be called on an AF_RXRPC socket more than once (currently maximum twice) to bind multiple listening services to it. There are some restrictions:
(1) All bind() calls involved must have a non-zero service ID.
(2) The service IDs must all be different.
(3) The rest of the address (notably the transport part) must be the same in all (a single UDP socket is shared).
(4) This must be done before listen() or sendmsg() is called.
This allows someone to connect to the service socket with different service IDs and lays the foundation for service upgrading.
The service ID used by an incoming call can be extracted from the msg_name returned by recvmsg().
Signed-off-by: David Howells <dhowells@redhat.com> 28036f44 Mon Jun 05 08:30:49 CDT 2017 David Howells <dhowells@redhat.com> rxrpc: Permit multiple service binding Permit bind() to be called on an AF_RXRPC socket more than once (currently maximum twice) to bind multiple listening services to it. There are some restrictions: (1) All bind() calls involved must have a non-zero service ID. (2) The service IDs must all be different. (3) The rest of the address (notably the transport part) must be the same in all (a single UDP socket is shared). (4) This must be done before listen() or sendmsg() is called. This allows someone to connect to the service socket with different service IDs and lays the foundation for service upgrading. The service ID used by an incoming call can be extracted from the msg_name returned by recvmsg(). Signed-off-by: David Howells <dhowells@redhat.com>
|
H A D | local_object.c | 28036f44 Mon Jun 05 08:30:49 CDT 2017 David Howells <dhowells@redhat.com> rxrpc: Permit multiple service binding
Permit bind() to be called on an AF_RXRPC socket more than once (currently maximum twice) to bind multiple listening services to it. There are some restrictions:
(1) All bind() calls involved must have a non-zero service ID.
(2) The service IDs must all be different.
(3) The rest of the address (notably the transport part) must be the same in all (a single UDP socket is shared).
(4) This must be done before listen() or sendmsg() is called.
This allows someone to connect to the service socket with different service IDs and lays the foundation for service upgrading.
The service ID used by an incoming call can be extracted from the msg_name returned by recvmsg().
Signed-off-by: David Howells <dhowells@redhat.com> 28036f44 Mon Jun 05 08:30:49 CDT 2017 David Howells <dhowells@redhat.com> rxrpc: Permit multiple service binding Permit bind() to be called on an AF_RXRPC socket more than once (currently maximum twice) to bind multiple listening services to it. There are some restrictions: (1) All bind() calls involved must have a non-zero service ID. (2) The service IDs must all be different. (3) The rest of the address (notably the transport part) must be the same in all (a single UDP socket is shared). (4) This must be done before listen() or sendmsg() is called. This allows someone to connect to the service socket with different service IDs and lays the foundation for service upgrading. The service ID used by an incoming call can be extracted from the msg_name returned by recvmsg(). Signed-off-by: David Howells <dhowells@redhat.com>
|
H A D | call_accept.c | 28036f44 Mon Jun 05 08:30:49 CDT 2017 David Howells <dhowells@redhat.com> rxrpc: Permit multiple service binding
Permit bind() to be called on an AF_RXRPC socket more than once (currently maximum twice) to bind multiple listening services to it. There are some restrictions:
(1) All bind() calls involved must have a non-zero service ID.
(2) The service IDs must all be different.
(3) The rest of the address (notably the transport part) must be the same in all (a single UDP socket is shared).
(4) This must be done before listen() or sendmsg() is called.
This allows someone to connect to the service socket with different service IDs and lays the foundation for service upgrading.
The service ID used by an incoming call can be extracted from the msg_name returned by recvmsg().
Signed-off-by: David Howells <dhowells@redhat.com> 28036f44 Mon Jun 05 08:30:49 CDT 2017 David Howells <dhowells@redhat.com> rxrpc: Permit multiple service binding Permit bind() to be called on an AF_RXRPC socket more than once (currently maximum twice) to bind multiple listening services to it. There are some restrictions: (1) All bind() calls involved must have a non-zero service ID. (2) The service IDs must all be different. (3) The rest of the address (notably the transport part) must be the same in all (a single UDP socket is shared). (4) This must be done before listen() or sendmsg() is called. This allows someone to connect to the service socket with different service IDs and lays the foundation for service upgrading. The service ID used by an incoming call can be extracted from the msg_name returned by recvmsg(). Signed-off-by: David Howells <dhowells@redhat.com>
|
H A D | af_rxrpc.c | 28036f44 Mon Jun 05 08:30:49 CDT 2017 David Howells <dhowells@redhat.com> rxrpc: Permit multiple service binding
Permit bind() to be called on an AF_RXRPC socket more than once (currently maximum twice) to bind multiple listening services to it. There are some restrictions:
(1) All bind() calls involved must have a non-zero service ID.
(2) The service IDs must all be different.
(3) The rest of the address (notably the transport part) must be the same in all (a single UDP socket is shared).
(4) This must be done before listen() or sendmsg() is called.
This allows someone to connect to the service socket with different service IDs and lays the foundation for service upgrading.
The service ID used by an incoming call can be extracted from the msg_name returned by recvmsg().
Signed-off-by: David Howells <dhowells@redhat.com> 28036f44 Mon Jun 05 08:30:49 CDT 2017 David Howells <dhowells@redhat.com> rxrpc: Permit multiple service binding Permit bind() to be called on an AF_RXRPC socket more than once (currently maximum twice) to bind multiple listening services to it. There are some restrictions: (1) All bind() calls involved must have a non-zero service ID. (2) The service IDs must all be different. (3) The rest of the address (notably the transport part) must be the same in all (a single UDP socket is shared). (4) This must be done before listen() or sendmsg() is called. This allows someone to connect to the service socket with different service IDs and lays the foundation for service upgrading. The service ID used by an incoming call can be extracted from the msg_name returned by recvmsg(). Signed-off-by: David Howells <dhowells@redhat.com>
|
H A D | ar-internal.h | 28036f44 Mon Jun 05 08:30:49 CDT 2017 David Howells <dhowells@redhat.com> rxrpc: Permit multiple service binding
Permit bind() to be called on an AF_RXRPC socket more than once (currently maximum twice) to bind multiple listening services to it. There are some restrictions:
(1) All bind() calls involved must have a non-zero service ID.
(2) The service IDs must all be different.
(3) The rest of the address (notably the transport part) must be the same in all (a single UDP socket is shared).
(4) This must be done before listen() or sendmsg() is called.
This allows someone to connect to the service socket with different service IDs and lays the foundation for service upgrading.
The service ID used by an incoming call can be extracted from the msg_name returned by recvmsg().
Signed-off-by: David Howells <dhowells@redhat.com> 28036f44 Mon Jun 05 08:30:49 CDT 2017 David Howells <dhowells@redhat.com> rxrpc: Permit multiple service binding Permit bind() to be called on an AF_RXRPC socket more than once (currently maximum twice) to bind multiple listening services to it. There are some restrictions: (1) All bind() calls involved must have a non-zero service ID. (2) The service IDs must all be different. (3) The rest of the address (notably the transport part) must be the same in all (a single UDP socket is shared). (4) This must be done before listen() or sendmsg() is called. This allows someone to connect to the service socket with different service IDs and lays the foundation for service upgrading. The service ID used by an incoming call can be extracted from the msg_name returned by recvmsg(). Signed-off-by: David Howells <dhowells@redhat.com>
|