From: Qingfang Deng <qingfang.deng@linux.dev>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Shuah Khan <shuah@kernel.org>,
linux-ppp@vger.kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: net: add socat syslog for PPPoL2TP
Date: Tue, 26 May 2026 23:23:36 +0800 [thread overview]
Message-ID: <7b39dacb-6c4c-430a-9bc8-4d53d4f1f404@linux.dev> (raw)
In-Reply-To: <60b50562-3351-49da-ab6b-953270380314@kernel.org>
On 5/26/2026 4:10 PM, Matthieu Baerts wrote:
> Hi Qingfang,
>
> On 26/05/2026 11:41, Qingfang Deng wrote:
>> As done in pppoe.sh, start socat as the syslog listener. In case the
>> test fails, dump its log to see what's going on.
>
> (...)
>
>> diff --git a/tools/testing/selftests/net/ppp/pppol2tp.sh b/tools/testing/selftests/net/ppp/pppol2tp.sh
>> index 5b592785f1f9..96786267ccc7 100755
>> --- a/tools/testing/selftests/net/ppp/pppol2tp.sh
>> +++ b/tools/testing/selftests/net/ppp/pppol2tp.sh
>
> (...)
>
>> +# Dump syslog messages if the test failed
>> +if [ "$RET" -ne 0 ]; then
>
> This only checks for errors with the first test, not with the second one
> below. Should you create a new helper and call it here and below? Or
> only once at the end, using ${EXIT_STATUS} instead?
I'll move it to the end, thanks.
>> + while read -r _sign _date _time len _from _to
>> + do len=${len##*=}
>> + read -n "$len" -r LINE
>> + echo "$LINE"
>> + done < "$PPPOL2TP_LOG"
>> +fi
>> +
>> # Recursion test
>> RET=0
>> # Delete route to LNS IP
>
> Cheers,
> Matt
>
prev parent reply other threads:[~2026-05-26 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 1:41 [PATCH net-next] selftests: net: add socat syslog for PPPoL2TP Qingfang Deng
2026-05-26 8:10 ` Matthieu Baerts
2026-05-26 15:23 ` Qingfang Deng [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7b39dacb-6c4c-430a-9bc8-4d53d4f1f404@linux.dev \
--to=qingfang.deng@linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox