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
| ||
|
Message-ID: <75f3cba0-4f4b-15ca-5cda-537fecd6b55b@kernel.org> Date: Thu, 11 May 2023 09:02:22 -0600 From: David Ahern <dsahern@...nel.org> To: Guillaume Nault <gnault@...hat.com>, David Miller <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Eric Dumazet <edumazet@...gle.com> Cc: netdev@...r.kernel.org Subject: Re: [PATCH v2 net-next 2/4] selftests: fcnal: Test SO_DONTROUTE on TCP sockets. On 5/11/23 8:39 AM, Guillaume Nault wrote: > Use nettest --{client,server}-dontroute to test the kernel behaviour > with TCP sockets having the SO_DONTROUTE option. Sending packets to a > neighbour (on link) host, should work. When the host is behind a > router, sending should fail. > > Client and server sockets are tested independently, so that we can > cover different TCP kernel paths. > > SO_DONTROUTE also affects the syncookies path. So ipv4_tcp_dontroute() > is made to work with or without syncookies, to cover both paths. > > Signed-off-by: Guillaume Nault <gnault@...hat.com> > --- > v2: Use 'nettest -B' instead of invoking two nettest instances for > client and server. > > tools/testing/selftests/net/fcnal-test.sh | 56 +++++++++++++++++++++++ > 1 file changed, 56 insertions(+) > Reviewed-by: David Ahern <dsahern@...nel.org>
Powered by blists - more mailing lists