News for hackers. Stuff that matters.
Re:A 24-year-old bug in the Linux Kernel TCP stack (2021) by omginternets on Monday October 17, 2022 @03:57PM (#33238750)
>I am wondering if it was put in to the kernel for 5.10 and then left "off by default" until this year.

Any idea how we might check that?

>I haven't had time to track down why, but it has stayed with newer kernels, too: 5.15.41, 5.15.59 also have this issue. I compiled 5.15.72 last night but i haven't rebooted yet.

I'm fairly certain we've seen it on `Linux 5.15.0-1017-aws x86_64`.

Re:A 24-year-old bug in the Linux Kernel TCP stack (2021) by genewitch on Tuesday October 18, 2022 @05:03AM (#33244714)
I could, i guess, try to load an old kernel. i tend to clean out /boot, and if the package manager deletes my kernel source all i have is a .config. I would lean toward .config diffs, but it is possible that my distribution kernel maintainers made specific patches that made this networking stuff "optional" - as is spectre and rowhammer and other speculative execution mitigation "optional". I just know my torment with networking started about 5 months ago at the closest. I didn't upgrade kernels between February and May 31st of 2022, so if it happened in there, i wouldn't be able to track that down without some sort of distro-specific archive of kernel releases.