Linux s390 Architecture development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Qingfang Deng" <qingfang.deng@linux.dev>, linux-s390@vger.kernel.org
Cc: "Heiko Carstens" <hca@linux.ibm.com>,
	"Vasily Gorbik" <gor@linux.ibm.com>,
	"Alexander Gordeev" <agordeev@linux.ibm.com>,
	"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [RFC net-next] ppp: remove BSD-Compress support
Date: Wed, 28 Oct 2026 06:38:36 +0000	[thread overview]
Message-ID: <sashiko-outbox-187565@kernel.org> (raw)
In-Reply-To: <20261028063452.25812-1-qingfang.deng@linux.dev>

> The BSD-Compress decoder assumes that accm is 32 bits, but declares it
> as unsigned long. On 64-bit systems, consumed code bits survive the
> left shift and corrupt the next code. An x86-64 PPP-over-PTY loopback
> test reproduces a fatal bad-code error on the first compressed packet.
> 
> pppd normally requests Deflate in preference to BSD-Compress when both
> methods can be negotiated. If BSD-Compress is selected and encounters
> this fatal error, pppd disables compression and logs:
> 
>   Lost compression sync: disabling compression
> 
> The link remains up and traffic can continue uncompressed.
> 
> The core compression routine has remained unchanged since Linux 2.1.67
> (1997), and the decompression routine since its introduction in Linux
> [ ... ]
> 
> OpenAI Codex assisted with the commit message, cleanup, and PTY testing.
> 
> Link: https://lore.kernel.org/netdev/20240812084312.14127-1-r.smirnov@omp.ru/
> Signed-off-by: Qingfang Deng <qingfang.deng@linux.dev>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261028063452.25812-1-qingfang.deng@linux.dev?part=1


      reply	other threads:[~2026-10-28  6:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28  6:33 [RFC net-next] ppp: remove BSD-Compress support Qingfang Deng
2026-10-28  6:38 ` sashiko-bot [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=sashiko-outbox-187565@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=qingfang.deng@linux.dev \
    --cc=sashiko-reviews@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox