Gabor, I could reproduce the bug using the upstream test (https://<email address hidden>/).
On 4.15.0-211-generic #222-Ubuntu I ended up with:
[ 31.286092] WARNING: CPU: 0 PID: 1088 at /build/linux-RlFMDZ/linux-4.15.0/net/core/stream.c:212 sk_stream_kill_queues+0xed/0x110
This was not reproducible with the testing version I provided above (4.15.0-211-generic #222+lp2020279.1).
I've also checked the trees of the other series:
trusty and xenial - not affected
bionic - affected
focal, jammy, kinetic, lunar, and mantic - include the fix already
Gabor, I could reproduce the bug using the upstream test (https://<email address hidden>/).
On 4.15.0-211-generic #222-Ubuntu I ended up with:
[ 31.286092] WARNING: CPU: 0 PID: 1088 at /build/ linux-RlFMDZ/ linux-4. 15.0/net/ core/stream. c:212 sk_stream_ kill_queues+ 0xed/0x110
This was not reproducible with the testing version I provided above (4.15.0-211-generic #222+lp2020279.1).
I've also checked the trees of the other series:
trusty and xenial - not affected
bionic - affected
focal, jammy, kinetic, lunar, and mantic - include the fix already
Given this, I have sent the fix to the mailing list: https:/ /lists. ubuntu. com/archives/ kernel- team/2023- June/140472. html