Re: [PATCH mptcp-next v11 00/10] Reduce the differences between TCP and MPTCP for TLS usage

[Matthieu Baerts <matttbe@kernel.org>]

Hi Geliang,

On 31/08/2026 10:50, Geliang Tang wrote:
> Hi Matt,
> 
> On Sun, 2026-08-30 at 15:33 +0000, MPTCP CI wrote:
>> Hi Geliang,
>>
>> Thank you for your modifications, that's great!
>>
>> Our CI did some validations and here is its report:
>>
>> - KVM Validation: normal (except selftest_mptcp_join): Unstable: 1
>> failed test(s): packetdrill_dss ⚠️ 
>> - KVM Validation: normal (only selftest_mptcp_join): Success! ✅
>> - KVM Validation: debug (except selftest_mptcp_join): Notice: Call
>> Traces at boot time, rebooted and continued ⚠️ 
>> - KVM Validation: debug (only selftest_mptcp_join): Notice: Call
>> Traces at boot time, rebooted and continued ⚠️ 
>> - KVM Validation: btf-normal (only bpftest_all): Success! ✅
>> - KVM Validation: btf-debug (only bpftest_all): Notice: Call Traces
>> at boot time, rebooted and continued - Notice: Call Traces at
>> shutdown time, ignored and continued ⚠️ 
>> - Task:
>> https://github.com/multipath-tcp/mptcp_net-next/actions/runs/33317921888
> 
> The latest code triggers a crash when running virtme:
> 
> BUG: sleeping function called from invalid context at
> include/linux/sched/mm.h:322
> 
> [    4.595485][    T1] virtme-ng-init: mount devtmpfs -> /dev: EBUSY:
> Device or resource busy
> Waiting for the virtme-ng-init to finish
> [    4.598085][    T1] virtme-ng-init: Setting hostname to mptcpdev...
> [    4.630121][    T1] virtme-ng-init: running systemd-tmpfiles
> [    5.434499][   T70] systemd-tmpfile (70) used greatest stack depth:
> 24904 bytes left
> [    5.434526][   T70] BUG: sleeping function called from invalid
> context at include/linux/sched/mm.h:322
> [    5.434529][   T70] in_atomic(): 1, irqs_disabled(): 1, non_block:
> 0, pid: 70, name: systemd-tmpfile
> [    5.434532][   T70] preempt_count: 2, expected: 0
> [    5.434534][   T70] RCU nest depth: 0, expected: 0
> [    5.434536][   T70] locks held by systemd-tmpfile/70: 5, last CPU#1:
> [    5.434539][   T70]  #0: ffffffff84a3d078 (low_water_lock){+.+.}-
> {3:3}, at: do_exit (include/linux/spinlock.h:347)
> [    5.434558][   T70]  #1: ffffffff84badda0 (console_lock){+.+.}-
> {0:0}, at: vprintk_emit (kernel/printk/printk.c:2478)
> [    5.434569][   T70]  #2: ffffffff84bade18 (console_srcu){....}-
> {0:0}, at: console_flush_one_record (include/linux/rcupdate.h:314
> (discriminator 1))
> [    5.434578][   T70]  #3: ffffffff84acd740 (console_owner){....}-
> {0:0}, at: console_lock_spinning_enable (kernel/printk/printk.c:1902
> (discriminator 1))
> [    5.434587][   T70]  #4: ffffffff84acd640 (printk_legacy_map-wait-
> type-override){....}-{3:3}, at: console_emit_next_record
> (kernel/printk/printk.c:3095 (discriminator 1))
> [    5.434596][   T70] irq event stamp: 273968
> [    5.434598][   T70] hardirqs last  enabled at (273967):
> __down_trylock_console_sem (kernel/printk/printk.c:330 (discriminator
> 5))
> [    5.434604][   T70] hardirqs last disabled at (273968):
> console_emit_next_record (kernel/printk/printk.c:3176 (discriminator
> 7))
> [    5.434609][   T70] softirqs last  enabled at (273890):
> handle_softirqs (kernel/softirq.c:491)
> [    5.434614][   T70] softirqs last disabled at (273865):
> __irq_exit_rcu (kernel/softirq.c:679)
> [    5.434619][   T70] Preemption disabled at:
> 
> I have already fixed this over the weekend and sent the patch to the
> virtualization mailing list:
> 
> https://lore.kernel.org/virtualization/e084d7ed4c03020da3de5cbe1eb3a0c2055cbbd6.1787966331.git.tanggeliang@kylinos.cn/T/#u
> 
> Please consider applying this patch first to avoid CI failures.
Thank you for this message and for the fix. It looks like the same patch
has already been sent before on the virtualisation ML. I took the oldest
one because I guess that's the one which will be applied:

https://lore.kernel.org/20260810-serial-v1-1-abbe51602c13@debian.org

New patches for t/upstream-net and t/upstream:
- 37d601ecd030: virtio_console: allocate the port_buffer with the
caller's gfp
- Results: 55dc409a2258..f53fe5e25d9e (export-net)
- Results: b301d9e1afdc..edf6a01ba9f7 (export)

Tests are now in progress:

- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/0c164b6dd50adfb4bb924b9030ab3e529a1b48cc/checks
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/52ef5e042a881a7753cad4d5e3c3f5c15676da17/checks

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.