All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Qingfang Deng <qingfang.deng@linux.dev>
Cc: pali@kernel.org, linux-ppp@vger.kernel.org,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, arnd@arndb.de,
	gnault@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] pppox: drain queued packets on channel handoff
Date: Mon, 17 Aug 2026 21:10:06 +0000	[thread overview]
Message-ID: <178700100689.1739106.5852126263750575730.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260811035314.302878-1-qingfang.deng@linux.dev>

Hello:

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

On Tue, 11 Aug 2026 11:53:10 +0800 you wrote:
> PPPIOCGCHAN both returns the channel index and marks a PPPOX socket as
> bound to generic PPP, despite its getter semantic. Packets received
> before that transition are queued on sk_receive_queue, but a bound
> socket is no longer readable. Such packets therefore remain queued until
> the socket is destroyed.
> 
> After marking a socket bound, wait for receive paths that observed the
> old state to finish queueing packets, and then drain the queue into
> generic PPP.
> 
> [...]

Here is the summary with links:
  - [net] pppox: drain queued packets on channel handoff
    https://git.kernel.org/netdev/net/c/92c1bf630abf

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-08-17 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11  3:53 [PATCH net] pppox: drain queued packets on channel handoff Qingfang Deng
2026-08-13  0:15 ` Jakub Kicinski
2026-08-13  4:01   ` Qingfang Deng
2026-08-17 21:10 ` 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=178700100689.1739106.5852126263750575730.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gnault@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ppp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pali@kernel.org \
    --cc=qingfang.deng@linux.dev \
    /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.