On Sun, Mar 31, 2024 at 04:05:57PM +0300, Vitaliy Makkoveev wrote:
> Syzkaller found that SOCK_DGRAM coould became listening socket, which is
> wrong.
> 
> 1. https://syzkaller.appspot.com/bug?extid=00450333592fcd38c6fe

I looked in 4.4BSD, it looks like this was always allowed.  The
only thing it did, was to set SO_ACCEPTCONN.  And the code did not
care.  But now, with locking and assert it gets relevant.

Setting SO_ACCEPTCONN on SOCK_DGRAM makes not sense.  Better fail
early.

OK bluhm@

> Index: sys/kern/uipc_socket.c
> ===================================================================
> RCS file: /cvs/src/sys/kern/uipc_socket.c,v
> retrieving revision 1.323
> diff -u -p -r1.323 uipc_socket.c
> --- sys/kern/uipc_socket.c	27 Mar 2024 22:47:53 -0000	1.323
> +++ sys/kern/uipc_socket.c	31 Mar 2024 13:04:01 -0000
> @@ -231,6 +231,14 @@ solisten(struct socket *so, int backlog)
>  	int sominconn_local = READ_ONCE(sominconn);
>  	int error;
>  
> +	switch (so->so_type) {
> +	case SOCK_STREAM:
> +	case SOCK_SEQPACKET:
> +		break;
> +	default:
> +		return (EOPNOTSUPP);
> +	}
> +
>  	soassertlocked(so);
>  
>  	if (so->so_state & (SS_ISCONNECTED|SS_ISCONNECTING|SS_ISDISCONNECTING))