From: Qingfang Deng <dqfext@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Shuah Khan <shuah@kernel.org>,
"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>,
Felix Maurer <fmaurer@redhat.com>,
Antonio Quartulli <antonio@openvpn.net>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-ppp@vger.kernel.org, netdev@vger.kernel.org,
Paul Mackerras <paulus@ozlabs.org>,
Guillaume Nault <gnault@redhat.com>
Subject: Re: [PATCH net-next v4] selftests: net: add tests for PPP
Date: Thu, 26 Mar 2026 16:26:23 +0800 [thread overview]
Message-ID: <CALW65jYdzn_rZWa2zwYd5J+Gd=kyaGMsVFyX0fMJfKfgULMO6w@mail.gmail.com> (raw)
In-Reply-To: <20260326081304.xKa7-s_1@linutronix.de>
Hi Sebastian,
On Thu, Mar 26, 2026 at 4:13 PM Sebastian Andrzej Siewior
<bigeasy@linutronix.de> wrote:
>
> On 2026-03-26 10:16:24 [+0800], Qingfang Deng wrote:
> > Add ping and iperf3 tests for ppp_async.c and pppoe.c.
>
> Oh thank you for doing this.
> I haven't look in detail but this cover the "invalid loop" cases that
> ppp tries to catch?
By "invalid loop", do you mean transmit recursion?
https://lore.kernel.org/all/20250715150806.700536-2-bigeasy@linutronix.de/
AFAIK, this can only happen with PPTP or L2TP, which were not included
in this patch.
Add Cc: Guillaume Nault
Regards,
Qingfang
next prev parent reply other threads:[~2026-03-26 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 2:16 [PATCH net-next v4] selftests: net: add tests for PPP Qingfang Deng
2026-03-26 8:13 ` Sebastian Andrzej Siewior
2026-03-26 8:26 ` Qingfang Deng [this message]
2026-03-26 8:30 ` Sebastian Andrzej Siewior
2026-03-26 9:08 ` Qingfang Deng
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='CALW65jYdzn_rZWa2zwYd5J+Gd=kyaGMsVFyX0fMJfKfgULMO6w@mail.gmail.com' \
--to=dqfext@gmail.com \
--cc=antonio@openvpn.net \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fmaurer@redhat.com \
--cc=gnault@redhat.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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulus@ozlabs.org \
--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