lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 16 Mar 2019 12:19:02 -0700 (PDT) From: David Miller <davem@...emloft.net> To: jon.maloy@...csson.com Cc: netdev@...r.kernel.org, gordan.mihaljevic@...tech.com.au, tung.q.nguyen@...tech.com.au, hoang.h.le@...tech.com.au, canh.d.luu@...tech.com.au, ying.xue@...driver.com, tipc-discussion@...ts.sourceforge.net Subject: Re: [net 1/1] tipc: allow service ranges to be connect()'ed on RDM/DGRAM From: Jon Maloy <jon.maloy@...csson.com> Date: Fri, 15 Mar 2019 21:11:00 +0100 > @@ -2349,6 +2349,16 @@ static int tipc_wait_for_connect(struct socket *sock, long *timeo_p) > return 0; > } > > +static int tipc_sockaddr_is_sane(struct sockaddr_tipc *addr) > +{ > + if (addr->family != AF_TIPC) > + return 0; I think bool and true/false are most appropriate for this function.
Powered by blists - more mailing lists