The Latest Kernel Release.

onebuck · 11-10-2017, 03:00 PM

Hi,

Quote:

Originally Posted by igadoter

Please remove this thread. There is sub-forum in Software forum, where kernel is being discussed. If someone is interested in kernel development, I think this is the first place to look at. As I remember Slackware always uses "plan, vanilla kernel", so there is not much to discuss about kernel here. At least someone want/need patch kernel running Slackware. Cheers.

I see no need to move/remove this thread from the <Slackware> forum.As others have stated we as Slackware users do desire to have communication within this forum about/related to the kernel. Our information exchange here helps the many Slackware users.

So if you do not care for this thread then I suggest that you use the ignore option that is available to you.

Hope this helps.
Have fun & enjoy!

ttk · 11-10-2017, 05:23 PM

Please don't delete or move this thread. It is highly relevant for (for instance) keeping legacy Slackware 14.1 systems patched against current security vulnerabilities.

volkerdi · 11-10-2017, 07:34 PM

I find this to be a useful thread and would hate to see it go. My $0.02, if it counts for anything.

cwizardone · 11-12-2017, 03:48 PM

It's here!
The latest Stable Kernel, 4.14, has been released!

The complete change log, https://kernelnewbies.org/Linux_4.14

The tarball, https://cdn.kernel.org/pub/linux/ker...ux-4.14.tar.xz

AlleyTrotter · 11-12-2017, 08:35 PM

running 4.14 now
no problems
Would be nice to see a Slackware .config as its a LTS kernel
john

GazL · 11-13-2017, 04:11 AM

Only new config option of note for me was:

Code:

CONFIG_SLAB_FREELIST_HARDENED:
Many kernel heap attacks try to target slab cache metadata and
other infrastructure. This options makes minor performance
sacrifies to harden the kernel slab allocator against common
freelist exploit methods.

Apparently this has a 0.07% ish overhead, so might be worth considering. I went with the initial setting of 'N' as my attack surface is very small, but I may revisit this option in future once the feature has had time to settled in.

Anyway, building in the background as I type...

Aeterna · 11-13-2017, 07:40 AM

broken virtualbox
USB issues not fixed (doubt that ever will be..)

bassmadrigal · 11-13-2017, 08:22 AM

Quote:

Originally Posted by Aeterna

broken virtualbox
USB issues not fixed (doubt that ever will be..)

Is VirtualBox itself broken or just USB pass through in VirtualBox. I ask because I was running the RCs of 4.14 and I couldn't ever get VirutalBox to build from source (my preferred method). It complaining about qt5 not being compiled with -std=c++11, even though I tried compiling it with it forced -- I think it is because 14.2's GCC is too old, but that's just speculation on my part. I installed it using the official binary and it installs fine and AFAIK, it allows VMs to run (although, I haven't started it up for a bit... I should check when I get home).

kjhambrick · 11-13-2017, 08:30 AM

All --

Kernels 3.16.50 and 3.2.95 are now available.

Handy Links:

Code:

longterm:  3.16.50 Source ChangeLog [CVE] 2017-11-11
longterm:  3.2.95  Source ChangeLog [CVE] 2017-11-11 ( Slackware-14.0 )

CVE References:

ChangeLog-3.16.50 references CVE-2017-0786, CVE-2017-12193, CVE-2017-13080 and CVE-2017-15265.

ChangeLog-3.2.95 references CVE-2017-13080 and CVE-2017-15265.

Check for the Latest Updates at www.kernel.org.

Have Fun All'Y'All !

-- kjh

Aeterna · 11-13-2017, 09:57 AM

Quote:

Originally Posted by bassmadrigal

Is VirtualBox itself broken or just USB pass through in VirtualBox. I ask because I was running the RCs of 4.14 and I couldn't ever get VirutalBox to build from source (my preferred method). It complaining about qt5 not being compiled with -std=c++11, even though I tried compiling it with it forced -- I think it is because 14.2's GCC is too old, but that's just speculation on my part. I installed it using the official binary and it installs fine and AFAIK, it allows VMs to run (although, I haven't started it up for a bit... I should check when I get home).

What I see is that there are two sources of vbox issues:
1) 4.14 kernel
- Slackware current host
VirtualBox-5.1.30-118389-Linux_amd64.run broken

VirtualBox-5.2.0-118431-Linux_amd64.run
even if you get VB installed the only module that will compile is vboxdrv
all clients are just super slow

2) oracle virtualbox software
- I have installed latest available:
VirtualBox-5.2.0-118431-Linux_amd64.run
VBoxGuestAdditions_5.2.1-118918.iso
Oracle_VM_VirtualBox_Extension_Pack-5.2.0-118431.vbox-extpack

Slackware-current VB host with kernel-4.13.12:
clients are slow:
- Slackware current client is unbearably slow with VBoxGuestAdditions_-5.2
- Devuan CERES/ASCII:
ASCII has VBoxGuestAdditions_-5.1.30
CERES has VBoxGuestAdditions_-5.2
both with LXDE
in both cases GUI works well but console is slow
-Funtoo VBoxGuestAdditions_5.1.30
this is the only one not affected
- OpenIndiana refuses to work even with VBoxGuestAdditions_5.1.30
- Windows 8.1 VBoxGuestAdditions_5.1.30 slow

if you build VBoxGuestAdditions_5.2 for linux-4.13.12
guests will suffer still from above issues

3) VB guest slowness is related to VirtualBox-5.2.0-118431-Linux_amd64.run (host)
- with VirtualBox-5.1.30-118389-Linux_amd64.run on host
and VBoxGuestAdditions_5.2.1-118918.iso installed on guest
all is fast and nice

I am going back to 5.1.30 and kernel 4.13.12 and wait for fixes.

USB - I was referring to kernel USB security issues (14) but I doubt these will get fixed as it seem not important

(edited for some clarification)

montagdude · 11-13-2017, 11:00 AM

Quote:

Originally Posted by bassmadrigal

@bamunds, I think the "plain vanilla" is based on us not using patches in our kernel like many distros do.

I dislike the term "vanilla" as it is commonly used to refer to software with minimal patching relative to upstream. If vanilla is plain, then why do they sell both plain and vanilla yogurt at the grocery store?

hitest · 11-13-2017, 11:42 AM

Quote:

Originally Posted by montagdude

I dislike the term "vanilla" as it is commonly used to refer to software with minimal patching relative to upstream.

What should it be called? Pure? Unaltered? The_real_stuff? Sorry, but, I couldn't resist. Heh-heh.

I'm fine with the designation vanilla.

cwizardone · 11-13-2017, 11:56 AM

Quote:

Originally Posted by Aeterna

......I am going back to 5.1.30 and kernel 4.13.12 and wait for fixes.....

I've been using the 4.13.12 kernel and VirtualBox-5.1.28-117968, without any problems.
This isn't the first time there has been a USB conflict between the kernel and VirtualBox. The last time it happen it was quickly repaired in a kernel update.

montagdude · 11-13-2017, 11:57 AM

Quote:

Originally Posted by hitest

What should it be called? Pure? Unaltered? The_real_stuff? Sorry, but, I couldn't resist. Heh-heh.

I'm fine with the designation vanilla.

How about "organic?" (Just kidding, I dislike that term even more.)

bassmadrigal · 11-13-2017, 12:34 PM

Quote:

Originally Posted by Aeterna

What I see is that there are two sources of vbox issues:
1) 4.14 kernel
- Slackware current host
VirtualBox-5.1.30-118389-Linux_amd64.run broken

VirtualBox-5.2.0-118431-Linux_amd64.run
even if you get VB installed the only module that will compile is vboxdrv
all clients are just super slow

I will admit that I am doing this on a 14.2 install, not -current. And I also remembered that I was actually running a development snapshot because of some issues I had with the regular stable (but I don't remember what now). I just checked and my development snapshot was VirtualBox-5.2.1-118893-Linux_amd64.run, which has now been superseded by VirtualBox-5.2.1-119001-Linux_amd64.run. If you want to pursue this route, you can try the Guest Additions (118995) and Extension Pack (118994) from the Development Snapshot section on their TestBuilds page.

I'll have to try to remember to try out my VM when I get home to see how it runs. I don't remember anything crazy, but I didn't use it for very long.