LWN.net's Journal
[Most Recent Entries]
[Calendar View]
Thursday, March 26th, 2020
Time |
Event |
1:09a |
[$] LWN.net Weekly Edition for March 26, 2020 The LWN.net Weekly Edition for March 26, 2020 is available. | 12:37p |
Security updates for Thursday Security updates have been issued by CentOS (firefox, icu, kernel-rt, libvncserver, python-imaging, python-pip, python-virtualenv, thunderbird, tomcat, tomcat6, and zsh), Debian (icu and okular), Fedora (libxslt and php), Gentoo (bluez, chromium, pure-ftpd, samba, tor, weechat, xen, and zsh), Oracle (libvncserver), Red Hat (ipmitool and zsh), and SUSE (python-cffi, python-cryptography and python-cffi, python-cryptography, python-xattr). | 3:02p |
Plasma on TV: Presenting Plasma Bigscreen (KDE.News) The KDE.News site is carrying an announcement for the Plasma Bigscreen environment, which is meant for large-screen televisions. " Talking of interacting from the couch, voice control provides users with the ultimate comfort when it comes to TV viewing. But most big brands not only do not safeguard the privacy of their customers, but actively harvest their conversations even when they are not sending instructions to their TV sets. We use Mycroft's Open Source voice assistant to solve this problem." | 6:28p |
[$] Avoiding retpolines with static calls January 2018 was a sad time in the kernel community. The Meltdown and Spectre vulnerabilities had finally been disclosed, and the required workarounds hurt kernel performance in a number of ways. One of those workarounds — retpolines — continues to cause pain, with developers going out of their way to avoid indirect calls, since they must now be implemented with retpolines. In some cases, though, there may be a way to avoid retpolines and regain much of the lost performance; after a long gestation period, the "static calls" mechanism may finally be nearing the point where it can be merged upstream. | 8:56p |
Malcolm: Static analysis in GCC 10 David Malcolm writes about the static-analysis features that he is working on adding to the GCC compiler. " This issue is, of course, a huge problem to tackle. For this release, I’ve focused on the kinds of problems seen in C code—and, in particular double-free bugs—but with a view toward creating a framework that we can expand on in subsequent releases (when we can add more checks and support languages other than C)." |
|