Kernel 3.16.72 is available now at www.kernel.org:
https://cdn.kernel.org/pub/linux/ker...3.16.72.tar.xz
https://cdn.kernel.org/pub/linux/ker...ngeLog-3.16.72

Pat has released for stable the most recent kernel 4.4.189 with the latest mitigations for Spectre. http://www.slackware.com/changelog/s...php?cpu=x86_64 Follow the instructions for loading.
I do have one need beyond Pat's general config for his conmpile, it does not include FANOTIFY_ACCESS_PERMISSIONS=Y, which is needed for checking malware during on-access for both CLAMAV and Sophos Antivirus for Linux. I understand some features can be setup as a module for later loading, but this feature is either on or off, it is off, so on-access scanning fails. My limited knowledge is telling me that only a new config and kernel build will resolve this setting.

Short of recompiling from source, which I've been doing for over a year, is there a way to simply turn that feature on during the system boot load of the kernel, maybe something in init?

Appreciate advice, Cheers, Brian

Another round of updates has been scheduled for release on Friday afternoon, GMT.

If no problems are found while testing the release candidates, they might be available late Thursday (depending on your time zone).

5.2.9, will accommodate 144 patches.

4.19.67, will have 91 patches.

4.14.139, will contain 69 patches.

There's nothing I'm aware of that can change this feature in the kernel. I believe it is only configurable when compiling.

4.19.67 is now available

Kernel updates 5.2.9, 4.19.67 and 4.14.139 are now available at

https://www.kernel.org/

The change logs,

https://cdn.kernel.org/pub/linux/ker...hangeLog-5.2.9

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.19.67

https://cdn.kernel.org/pub/linux/ker...geLog-4.14.139

Has been added to the kernel-source packages in -current according to the latest ChangLogs:

An update for the 3.16.y kernel series has been scheduled for release late Monday evening, GMT.

The 3.16.73 update will have 4 patches.

Mr. Hutchings' announcement, http://lkml.iu.edu/hypermail/linux/k...8.2/01120.html

That is encouraging. I wonder if Pat will add it to the stable 4.4.x releases also? Cheers, BrianA_MN

5.3-rc5

The newest "mainline" development kernel, version 5.3-rc5, has been been made available for testing.

The tarball, https://git.kernel.org/torvalds/t/linux-5.3-rc5.tar.gz

Mr. Torvalds' announcement, http://lkml.iu.edu/hypermail/linux/k...8.2/01540.html

Well now, normally I won't add new features to a stable release, but I was actually entertaining that idea when the next 4.4.x fixing a CVE comes out. The option is getting tested in -current, seems like all the other distros have enabled it for a while... any objections?

I certainly don't have any objection! Thanks for considering it. Cheers, BrianA_MN

No objection from me, and I'd go as far as suggesting that you ship a 4.19 kernel in 14.2. I have been using that and shipping it in Slint since five months with no issue reported (admittedly from a very small users base). Maybe on the occasion of a new CVE fix appearing here? This, as firmware updates, could help people with a relatively new hardware not yet supported by 4.4.x to install Slackware 14.2.

4.19.x has an EOL of December 2020 though, whereas 4.4.x's EOL is Feb 2022, so from that perspective at least it makes sense to stay with 4.4.x.

https://www.kernel.org/category/releases.html

Something definitive's going to have to happen with 15.0 though: 5.4 has been confirmed LTS but its EOL is Dec 2021. Now that's no way long enough for Slackware 15.0 and earlier than I, for one, expected.

I think Pat's going to have to change kernels during 15.0 or release 15.1 soon thereafter, since waiting to see what happens with the 5.9 kernel would mean 15.0 not releasing until 2021, or late 2020 at the earliest.

I suggested 4.19.x because that's what Pat provides for -current , so the same kernels could be provided for both -current and 14.2: no more work but still would help users with new hardware and not wanting or able to run -current.