All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Qingfang Deng <qingfang.deng@linux.dev>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, kees@kernel.org,
	horms@kernel.org, manizada@pm.me, ericwouds@gmail.com,
	nbd@nbd.name, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] pppoe: delete session hash entries by pointer match
Date: Thu, 22 Oct 2026 00:30:13 +0000	[thread overview]
Message-ID: <179262901348.1378903.6285875327252867524.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261020092118.47416-1-qingfang.deng@linux.dev>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 20 Oct 2026 17:21:11 +0800 you wrote:
> pppoe_connect() copies the requested PPPoE address to a socket before
> attempting to insert the socket into the session hash table. If the
> tuple already exists, __set_item() returns -EALREADY, but the copied
> address and ifindex remain set on the failed socket.
> 
> Closing that socket then deletes the existing socket's hash entry
> through pppoe_release(), preventing it from receiving further session
> traffic. An unprivileged process in the same network namespace can
> trigger this through a duplicate connection attempt.
> 
> [...]

Here is the summary with links:
  - [net] pppoe: delete session hash entries by pointer match
    https://git.kernel.org/netdev/net/c/b5b8c81836e2

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-22  0:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20  9:21 [PATCH net] pppoe: delete session hash entries by pointer match Qingfang Deng
2026-10-20  9:24 ` netdev-bot+sinfo
2026-10-20  9:36   ` Qingfang Deng
2026-10-22  0:30 ` 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=179262901348.1378903.6285875327252867524.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=ericwouds@gmail.com \
    --cc=horms@kernel.org \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manizada@pm.me \
    --cc=nbd@nbd.name \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=qingfang.deng@linux.dev \
    --cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.