points by tptacek 1 day ago | 0 comments
Hey, I don't write AI blog posts. But I want to know how KVM escapes work, too.
[–] otterley 8 hours ago
You make it sound like uncritically tolerating AI slop is a nonnegotiable price of learning new things.
[–] tptacek 8 hours ago
It is when the "AI slop" is literally the only source of time-sensitive information, as it is here.
[–] otterley 7 hours ago
The time sensitive part containing the patch (which was also sloppy) was published last month; this article is but a PoC.
https://lore.kernel.org/netdev/20260922030310.8684-2-habte.y...
Anyway, I think you keep missing my point. It’s the “uncritical” word that is important here. How work is done is often as important as the work itself. Isn’t that what we teach our children and our junior colleagues? What’s more, expectations should be even higher with seniority.
[–] sscaryterry 16 hours ago
[–] tptacek 16 hours ago
[–] sscaryterry 12 hours ago
Ruby is not Rails. The same way Linux KVM is not Firecracker. You cannot paint everything with the same brush. The author chose to make this sensationalist by implying its a firecracker issue. It is not.
I've repeatedly explained this.
[–] tptacek 11 hours ago
Not for nothing, but it would have been possible for Firecracker to disable the partial checksum feature this vulnerability exploits. If you wanted to push on the argument a bit, you could say that Firecracker ran virtio-net in an aggressive and possibly unsafe configuration. I wouldn't agree, but it's a colorable argument.