accel-ppp.git/.github/workflows, branch sstp-ppposeq

sstp: add ppposeq transport to avoid userspace HDLC framing

2026-08-02T20:06:01+00:00

A pty is a byte stream, so the tty flip buffer merges frames written back to back and sstp has to re-delimit them with async HDLC escaping and a CRC-16 FCS. On a 1452-byte payload that is ~3600 ns per frame, most of it spent on the FCS. PPPOSEQ is a pppox protocol whose socket is the ppp endpoint itself, so one datagram is one frame and no framing is needed at all. The same payload takes ~380 ns per frame, about 9 times less. Requires kernel 2.6.37, the first with PX_MAX_PROTO 3, whose remaining slot it claims. Supported kernels are from 2.6.37 to 7.2. The new ppp-mode option selects the transport; auto, the default, falls back to async when the module is unavailable, so hosts with prebuilt kernels are unaffected. PPP_SYNC is removed, being disabled and unfixable over a pty: frame boundaries cannot be recovered from the stream, and coalescing cannot be prevented since frames arrive from the network stack.

ci: harden s390x qemu test against modloop/disk flakes

2026-06-10T12:57:46+00:00

The s390x netboot initramfs ships virtio_net but not virtio_blk; the block driver only becomes available after the modloop image is downloaded over the network at boot. When that download fails, sshd still comes up but /dev/vda never appears and setup-disk dies with "/dev/vda is not a block device suitable for partitioning". - Wait for /sys/block/vda/device before running setup-alpine, restarting the modloop and hwdrivers services on each retry. - Log the QEMU console (screen -L) for both VM launches and dump the logs at the end of the job, so failures of the second boot (the other recurring flake, where ssh never comes back after reboot) are debuggable. Co-Authored-By: Claude Fable 5

ci: Tightening warning condition in dmesg checks

2026-05-03T23:58:15+00:00

The boot-time RETBleed: WARNING: Spectre v2 mitigation... line matches the broad WARNING: regex. The intent of that pattern was to catch kernel WARN_ON() splats, which always begin with WARNING: CPU:. We can tighten checks, to avoid false positive. Signed-off-by: Denys Fedoryshchenko

ci: fail workflows on kernel issues found in dmesg

2026-05-02T12:07:57+00:00

Recently i wasted several hours searching bug in workflows/userspace. Turned out in dmesg we had highly visible WARNING that we dont watch. After each test run, dump dmesg and grep for canonical kernel-issue markers (WARNING, BUG, Oops, kernel panic, GPF, KASAN, kernel UBSAN, soft/hard lockup, hung tasks, bad page state, invalid opcode). Fail the job if any are present, with a GitHub Actions error annotation. Until now, kernel WARNs from out-of-tree drivers (e.g. vlan_mon tripping the new ETH_P_ALL ptype_head WARN_ON in 6.6+) were silently swallowed by the existing 'Display processes and dmesg after tests' steps -- visible only if a human inspected the log. The check runs with if: always() so it triggers both on test failure and on test completion. Applied to all four workflows that load kernel modules: run-tests-asan-ubsan.yml, run-tests.yml (Test-in-Qemu, Test-in-Alpine, Test-in-GH, Test-in-GH-Coverage), run-tests-32bit.yml, and run-tests-bigendian.yml. P.S. Some whitespace churn included. Signed-off-by: Denys Fedoryshchenko

ci: add tests execution with asan and ubsan

2025-08-19T18:59:40+00:00

ci: add build in debian:forky container

2025-08-14T21:48:55+00:00

ci: add fedora:rawhide build to build with latest kernel

2025-07-03T17:43:43+00:00

ci: remove ubuntu 20 builds due to EOL of Standard Support

2025-06-12T22:53:27+00:00

Merge pull request #239 from nuclearcat/fix-tests

2025-05-07T20:13:50+00:00

(workflows): Ubuntu 20.04 is deprecated, removing it

2025-05-02T20:44:00+00:00

This tests failing now with following message: ``` This is a scheduled Ubuntu 20.04 retirement. Ubuntu 20.04 LTS runner will be removed on 2025-04-15. For more details, see https://github.com/actions/runner-images/issues/11101 ``` Signed-off-by: Denys Fedoryshchenko