Recently, we had an issue where getting info about the memory would have
helped better understanding what went wrong.

Let add it just in case for later.

Reviewed-by: Geliang Tang <geli...@kernel.org>
Signed-off-by: Matthieu Baerts (NGI0) <matt...@kernel.org>
---
 tools/testing/selftests/net/mptcp/mptcp_lib.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/testing/selftests/net/mptcp/mptcp_lib.sh 
b/tools/testing/selftests/net/mptcp/mptcp_lib.sh
index 
91a1d3b76e664bd95fc36310ac2e2c89bfba1aa1..051e289d79676c5feb9f46da67a08116548f4b47
 100644
--- a/tools/testing/selftests/net/mptcp/mptcp_lib.sh
+++ b/tools/testing/selftests/net/mptcp/mptcp_lib.sh
@@ -118,11 +118,11 @@ mptcp_lib_pr_err_stats() {
        echo -en "${MPTCP_LIB_COLOR_RED}"
        {
                printf "\nnetns %s (listener) socket stat for %d:\n" "${lns}" 
"${port}"
-               ip netns exec "${lns}" ss -Menita -o "sport = :${port}"
+               ip netns exec "${lns}" ss -Menitam -o "sport = :${port}"
                cat "${lstat}"
 
                printf "\nnetns %s (connector) socket stat for %d:\n" "${cns}" 
"${port}"
-               ip netns exec "${cns}" ss -Menita -o "dport = :${port}"
+               ip netns exec "${cns}" ss -Menitam -o "dport = :${port}"
                [ "${lstat}" != "${cstat}" ] && cat "${cstat}"
        } 1>&2
        echo -en "${MPTCP_LIB_COLOR_RESET}"

-- 
2.47.1


Reply via email to