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, leitao@debian.org,
tristan@talencesecurity.com, hataegu0826@gmail.com,
norbert@doyensec.com, Brice.Goglin@ens-lyon.org, akpm@osdl.org,
Matt_Domsch@dell.com, paulus@ozlabs.org,
linux-ppp@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev-bot+sashiko@kernel.org
Subject: Re: [PATCH net] ppp: restore uncompressed fallback during CCP negotiation
Date: Thu, 12 Nov 2026 19:20:11 +0000 [thread overview]
Message-ID: <179451121152.604801.16504171266860549530.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261111155112.149204-1-qingfang.deng@linux.dev>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 11 Nov 2026 23:51:11 +0800 you wrote:
> ppp_ccp_peek() enables SC_COMP_RUN when sending a CCP Configure-Ack,
> before userspace sets SC_CCP_UP. Data traffic during this window can
> reach pad_compress_skb() while CCP is still negotiating. If compression
> succeeds, len is positive, but the SC_CCP_UP check fails and the packet
> falls through to the error path instead of being sent uncompressed.
>
> Deflate and BSD-Compress have already advanced their compression state
> by then. Dropping the packet can desynchronize with the peer's state,
> causing decompression errors.
>
> [...]
Here is the summary with links:
- [net] ppp: restore uncompressed fallback during CCP negotiation
https://git.kernel.org/netdev/net-next/c/f03ef07adfae
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-11-12 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 15:51 [PATCH net] ppp: restore uncompressed fallback during CCP negotiation Qingfang Deng
2026-11-12 19:20 ` 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=179451121152.604801.16504171266860549530.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Brice.Goglin@ens-lyon.org \
--cc=Matt_Domsch@dell.com \
--cc=akpm@osdl.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hataegu0826@gmail.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=norbert@doyensec.com \
--cc=pabeni@redhat.com \
--cc=paulus@ozlabs.org \
--cc=qingfang.deng@linux.dev \
--cc=tristan@talencesecurity.com \
/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.