From: patchwork-bot+netdevbpf@kernel•org
To: Qingfang Deng <qingfang.deng@linux•dev>
Cc: davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, horms@kernel•org, shuah@kernel•org,
linux-ppp@vger•kernel.org, netdev@vger•kernel.org,
linux-kselftest@vger•kernel.org, linux-kernel@vger•kernel.org,
matttbe@kernel•org
Subject: Re: [PATCH net-next] selftests: net: do not detect PPPoX loopback
Date: Sat, 06 Jun 2026 00:40:07 +0000 [thread overview]
Message-ID: <178070640715.3971808.7329061490220298966.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260603061746.23452-1-qingfang.deng@linux.dev>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Wed, 3 Jun 2026 14:17:44 +0800 you wrote:
> By default, pppd attempts to detect loopbacks on the underlying
> interface using a pseudo-randomly generated magic number and checks if
> the same value is received. The seed for the PRNG is a hash of hostname
> XOR current time XOR pid, which is likely to collide on NIPA, causing
> false positives. Disable magic number generation.
>
> Reported-by: Matthieu Baerts <matttbe@kernel•org>
> Fixes: 7af2a94f4dcf ("selftests: net: add tests for PPPoL2TP")
> Signed-off-by: Qingfang Deng <qingfang.deng@linux•dev>
>
> [...]
Here is the summary with links:
- [net-next] selftests: net: do not detect PPPoX loopback
https://git.kernel.org/netdev/net-next/c/2eb9a81a7f73
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-06 0:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 6:17 [PATCH net-next] selftests: net: do not detect PPPoX loopback Qingfang Deng
2026-06-06 0:40 ` patchwork-bot+netdevbpf [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=178070640715.3971808.7329061490220298966.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=linux-ppp@vger$(echo .)kernel.org \
--cc=matttbe@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=qingfang.deng@linux$(echo .)dev \
--cc=shuah@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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