On 7/8/18 11:24 PM, Lorenzo Colitti wrote: > On Sat, Jul 7, 2018 at 10:56 PM David Ahern <d...@cumulusnetworks.com> wrote: >>> Here is a packetdrill test : >> >> So I have to either learn how to use packetdrill or install a web server >> and put load on it. If the Android tests are not publicly available then >> the reference should be removed from the commit log. > > It is publicly available. The test is at > https://android.googlesource.com/kernel/tests/+/master/net/test/sock_diag_test.py > . Documentation is at > https://source.android.com/devices/architecture/kernel/network_tests . > > Note that not all the tests pass on upstream kernels. We do try to > keep them working, but because they are also run as conformance tests > for Android devices they must test out-of-tree behaviour, such as the > fact that unlike upstream, Android kernels use RFC-compliant SHA256 > truncation when the PF_KEY API is used. > > Again, I don't think you'll see this particular issue on the ARCH=um > tests that run by default. But if you run sock_diag_test.py on a VM or > physical machine as root, you should. >
ok. thanks for reference. I general I am always looking for more easy to run tests to catch problems like this.
