points by YetAnotherNick 1 day ago | 0 comments
> already discussed at length on HN
Couldn't find it. Care to provide link.
[–] tptacek 1 day ago
[–] catlifeonmars 1 day ago
That’s fascinating. I’ve seen this sort of thing on protocol implementations in layer 4+ but it’s rare to find it in layer 3.
[–] ytxm 1 day ago
Fixed a month ago upstream
https://github.com/torvalds/linux/commit/6785011f8b16abf40b1...
[–] sscaryterry 16 hours ago
And honestly, how the &*DK is this ANYTHING related to firecracker?
[–] markasoftware 1 day ago
Ah maybe not on HN, I forget where I learned of it. Either way, multiple weeks ago: https://news.ycombinator.com/item?id=50108845
Crucially, this happens in the middle of packet processing, so the kernel code is forced to work with two different ideas of how long the IPv4 header is. All hell predictably breaks loose.