Microsoft disables Spectre mitigations as Intel’s patches cause instability

Re:Microsoft disables Spectre mitigations as Intel’s patches... by quietbritishjim on Monday January 29, 2018 @08:38AM (#16257384)

This doesn't fully explain why a reboot is not required on Linux. If a *nix operating system updates sysfile1.so and sysfile2.so in the way you describe, then there will be some time where the filename sysfile1.so refers to the new version of that file while sysfile2.so refers to the old version. A program that is started in this brief window will get mixed versions of these libraries. It is unlikely that all combinations of versions of libraries have been tested together, so you could end up running with untested and possibly incompatible versions of libraries.

[ Parent | on HN ]

Re:Microsoft disables Spectre mitigations as Intel’s patches... by beagle3 on Monday January 29, 2018 @10:27AM (#16257985)

> This doesn't fully explain why a reboot is not required on Linux.

Of course there is a theoretical possibility that this will happen; however, in practice, updates (especially security updates) on Linux happen with ABI compatible libraries. E.g. on debian/ubuntu

apt-get update && apt-get upgrade

Will generally only do ABI compatible updates, without installing additional packages (you need 'dist-upgrade' or 'full-upgrade' for that).

Some updates will go as far as to prevent a program restart while updating (by temporarily making the executable unavailable).

Firefox on Ubuntu is an outlier - an update will replace it with one that isn't ABI compatible. It detects this and encourages you to restart it.

All in all, it's not that a reboot is never required for linux theoretically - it is that practically, you MUST reboot only for a kernel update, and may occasionally need to restart other programs that have been updated (but are rarely forced too).

[ Parent | on HN ]

Re:Microsoft disables Spectre mitigations as Intel’s patches... by snuxoll on Monday January 29, 2018 @09:25AM (#16257630)

This generally should never happen, Linux distributions don’t wholesale replace shared objects with ABI incompatible versions - soname’s exist to protect against this very issue.

[ Parent | on HN ]

Re:Microsoft disables Spectre mitigations as Intel’s patches... by CJefferson on Monday January 29, 2018 @11:36AM (#16258461)

I had a program with a rarely reported bug that turned out to be lazy loading of .so files that was this bug. Switched to eager loading and it went away.

[ Parent | on HN ]