An error occurred fetching the project authors.
  1. 08 Mar, 2024 4 commits
  2. 04 Mar, 2024 2 commits
  3. 27 Feb, 2024 3 commits
  4. 01 Feb, 2024 2 commits
  5. 02 Jan, 2024 1 commit
  6. 17 Dec, 2023 1 commit
    • Geliang Tang's avatar
      selftests: mptcp: join: fix subflow_send_ack lookup · c8f021ee
      Geliang Tang authored
      MPC backups tests will skip unexpected sometimes (For example, when
      compiling kernel with an older version of gcc, such as gcc-8), since
      static functions like mptcp_subflow_send_ack also be listed in
      /proc/kallsyms, with a 't' in front of it, not 'T' ('T' is for a global
      function):
      
       > grep "mptcp_subflow_send_ack" /proc/kallsyms
      
       0000000000000000 T __pfx___mptcp_subflow_send_ack
       0000000000000000 T __mptcp_subflow_send_ack
       0000000000000000 t __pfx_mptcp_subflow_send_ack
       0000000000000000 t mptcp_subflow_send_ack
      
      In this case, mptcp_lib_kallsyms_doesnt_have "mptcp_subflow_send_ack$"
      will be false, MPC backups tests will skip. This is not what we expected.
      
      The correct logic here should be: if mptcp_subflow_send_ack is not a
      global function in /proc/kallsyms, do these MPC backups tests. So a 'T'
      must be added in front of mptcp_subflow_send_ack.
      
      Fixes: 632978f0 ("selftests: mptcp: join: skip MPC backups tests if not supported")
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarGeliang Tang <geliang.tang@linux.dev>
      Reviewed-by: default avatarMat Martineau <martineau@kernel.org>
      Signed-off-by: default avatarMatthieu Baerts <matttbe@kernel.org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      c8f021ee
  7. 30 Nov, 2023 12 commits
  8. 15 Nov, 2023 1 commit
  9. 27 Oct, 2023 3 commits
  10. 19 Oct, 2023 2 commits
  11. 05 Aug, 2023 2 commits
  12. 01 Aug, 2023 3 commits
  13. 26 Jul, 2023 1 commit
  14. 19 Jul, 2023 1 commit
    • Matthieu Baerts's avatar
      selftests: mptcp: join: format subtests results in TAP · 7f117cd3
      Matthieu Baerts authored
      The current selftests infrastructure formats the results in TAP 13. This
      version doesn't support subtests and only the end result of each
      selftest is taken into account. It means that a single issue in a
      subtest of a selftest containing multiple subtests forces the whole
      selftest to be marked as failed. It also means that subtests results are
      not tracked by CIs executing selftests.
      
      MPTCP selftests run hundreds of various subtests. It is then important
      to track each of them and not one result per selftest.
      
      It is particularly interesting to do that when validating stable kernels
      with the last version of the test suite: tests might fail because a
      feature is not supported but the test didn't skip that part. In this
      case, if subtests are not tracked, the whole selftest will be marked as
      failed making the other subtests useless because their results are
      ignored.
      
      This patch formats subtests results in TAP in mptcp_join.sh selftest.
      
      In this selftest and before starting each subtest, the 'reset' function
      is called. We can then check if the previous test has passed, failed or
      has been skipped from there.
      
      Link: https://github.com/multipath-tcp/mptcp_net-next/issues/368Acked-by: default avatarPaolo Abeni <pabeni@redhat.com>
      Signed-off-by: default avatarMatthieu Baerts <matthieu.baerts@tessares.net>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      7f117cd3
  15. 14 Jul, 2023 2 commits