1. 10 7月, 2019 1 次提交
  2. 06 6月, 2019 1 次提交
    • S
      selftests: vm: Fix test build failure when built by itself · e2e88325
      Shuah Khan 提交于
      vm test build fails when test is built by itself using
      
      make -C tools/testing/selftests/vm
      or
      cd tools/testing/selftests/vm; make
      
      When the test is built invoking its Makefile directly, it defines
      OUTPUT which conflicts with lib.mk's logic to install headers.
      
      make --no-builtin-rules INSTALL_HDR_PATH=$OUTPUT/usr \
              ARCH=x86 -C ../../../.. headers_install
      make[1]: Entering directory '/mnt/data/lkml/linux_5.2'
        REMOVE  shmparam.h
      rm: cannot remove '/usr/include/asm-generic/shmparam.h': Permission denied
      scripts/Makefile.headersinst:96: recipe for target '/usr/include/asm-generic/.install' failed
      make[3]: *** [/usr/include/asm-generic/.install] Error 1
      scripts/Makefile.headersinst:32: recipe for target 'asm-generic' failed
      make[2]: *** [asm-generic] Error 2
      Makefile:1199: recipe for target 'headers_install' failed
      make[1]: *** [headers_install] Error 2
      make[1]: Leaving directory '/mnt/data/lkml/linux_5.2'
      ../lib.mk:52: recipe for target 'khdr' failed
      make: *** [khdr] Error 2
      
      Fixes: 8ce72dc3 ("selftests: fix headers_install circular dependency")
      Signed-off-by: NShuah Khan <skhan@linuxfoundation.org>
      e2e88325
  3. 05 6月, 2019 9 次提交
  4. 04 6月, 2019 1 次提交
    • X
      selftests: set sysctl bc_forwarding properly in router_broadcast.sh · 67c0aaa1
      Xin Long 提交于
      sysctl setting bc_forwarding for $rp2 is needed when ping_test_from h2,
      otherwise the bc packets from $rp2 won't be forwarded. This patch is to
      add this setting for $rp2.
      
      Also, as ping_test_from does grep "$from" only, which could match some
      unexpected output, some test case doesn't really work, like:
      
        # ping_test_from $h2 198.51.200.255 198.51.200.2
          PING 198.51.200.255 from 198.51.100.2 veth3: 56(84) bytes of data.
          64 bytes from 198.51.100.1: icmp_seq=1 ttl=64 time=0.336 ms
      
      When doing grep $form (198.51.200.2), the output could still match.
      So change to grep "bytes from $from" instead.
      
      Fixes: 40f98b9a ("selftests: add a selftest for directed broadcast forwarding")
      Signed-off-by: NXin Long <lucien.xin@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      67c0aaa1
  5. 31 5月, 2019 7 次提交
  6. 30 5月, 2019 5 次提交
  7. 29 5月, 2019 1 次提交
    • S
      selftests: pmtu: Fix encapsulating device in pmtu_vti6_link_change_mtu · 73f51d15
      Stefano Brivio 提交于
      In the pmtu_vti6_link_change_mtu test, both local and remote addresses
      for the vti6 tunnel are assigned to the same address given to the dummy
      interface that we use as encapsulating device with a known MTU.
      
      This works as long as the dummy interface is actually selected, via
      rt6_lookup(), as encapsulating device. But if the remote address of the
      tunnel is a local address too, the loopback interface could also be
      selected, and there's nothing wrong with it.
      
      This is what some older -stable kernels do (3.18.z, at least), and
      nothing prevents us from subtly changing FIB implementation to revert
      back to that behaviour in the future.
      
      Define an IPv6 prefix instead, and use two separate addresses as local
      and remote for vti6, so that the encapsulating device can't be a
      loopback interface.
      Reported-by: NXiumei Mu <xmu@redhat.com>
      Fixes: 1fad59ea ("selftests: pmtu: Add pmtu_vti6_link_change_mtu test")
      Signed-off-by: NStefano Brivio <sbrivio@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      73f51d15
  8. 27 5月, 2019 2 次提交
  9. 25 5月, 2019 13 次提交