Re:A cache invalidation bug in Linux memory management
by markjdb on Sunday September 30, 2018 @07:12PM
(#18108995)
You could say that about most bugs...
FreeBSD doesn't have a per-thread cache, but does similarly use a generation number to allow operations to detect stale state upon reacquiring the vm map lock. I don't see why it isn't prone to the same kinds of bugs.
Re:A cache invalidation bug in Linux memory management
by kolderman on Sunday September 30, 2018 @07:30PM
(#18109046)
I entirely disagree. You have have the most well thought out, architected, designed system in the world with:
if (i=0) {
Re:A cache invalidation bug in Linux memory management
by markjdb on Sunday September 30, 2018 @09:03PM
(#18109323)
You could argue that a system written in a language that permits such errors is not well-thought out. The terms you're using are not well-defined, so it's easy to disagree endlessly without arriving at a useful insight.
I wonder how freeBSD engineered this...Linux appears to grow organically at times.