SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Guest GPR values are live in the hardware GPRs at VM-exit. Do not
leave any guest values in hardware GPRs after the guest GPR values are
saved to the vcpu_vmx structure.
This is a partial mitigation for CVE 2017-5715 and CVE 2017-5753.
Specifically, it defeats the Project Zero PoC for CVE 2017-5715.
Last edited by cwizardone; 03-20-2018 at 10:23 AM.
No CVE References were found for 4.15.13, 4.14.30, 4.9.90, 4.4.124 or 3.18.102, but as always, do check the ChangeLogs for other security-related fixes.
if it contains a serious regression or security vulnerabilities.
Otherwise, people can just build their own kernel using the config and SlackBuild source provided.
It doesn't make sense to force people to restart the server every week to follow stable kernel releases
What criteria do they look for to update the kernel packages on the main site?
Good Q, Lysander666
I am not sure any more.
Maybe one of the Slackware Team members will chime in here ?
My $0.02: In the olden days, before all the Spectre / Meltdown ruckus, the team would release a Kernel Update only when serious security issues in the official Slackware Kernel were found and addressed in a newer Kernel.
For example, I ran 13.37 on my previous Laptop from 2011 until 2016 and I only recall one Upgrade for the 2.6.y Kernel in all those years.
These days, I am not quite sure, but I do trust Pat and the team to let one rip when we need it
And I am not in the habit of recommending third-party binary Packages ...
But I trust 55020 so here goes ...
If you want to try something newer and you don't want to build your own, there is the 'Dave's Unofficial Slackbuilt Kernels' ( dusk ) repo: https://dusk.idlemoor.tk/
HTH
-- kjh
EDIT: willysr posted a good answer much quicker than I posted my 'I dunno' answer
From Linus Torvalds <>
Date Sun, 1 Apr 2018 15:01:21 -0700
Subject Linux 4.16
So the take from final week of the 4.16 release looks a lot like rc7, in that about half of it is networking. If it wasn't for that, it would all be very small and calm.
We had a number of fixes and cleanups elsewhere, but none of it made me go "uhhuh, better let this soak for another week". And davem didn't think the networking was a reason to delay the release, so I'm not.
End result: 4.16 is out, and the merge window for 4.17 is open and I'll start doing pull requests tomorrow.
Outside of networking, most of the last week was various arch fixlets (powerpc, arm, x86, arm64), some driver fixes (mainly scsi and rdma) and misc other noise (documentation, vm, perf).
The appended shortlog gives an overview of the details (again, this is only the small stuff in the last week, if you want the full 4.16 changelog you'd better get the git tree and filter by your area of interest).
Linus
Last edited by cwizardone; 04-02-2018 at 06:03 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.