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.
I'm going to come right out and say this. LTS kernels... damned if you do, damned if you don't. Backporting breaks things, it's like trying to sew new arms on an octopus.
Quote:
Originally Posted by Patrick Volkerding in changelog
Thu Mar 19 01:45:30 UTC 2020
Don't bother with 5.4.26 folks, just wait for the next one. Trust me
That's atrocious, upgrading in good faith expecting bug fixes and having those bug fixes break things in the kernel.
The regression seems to be introduced in v4.7 with:
1f60fbe72749 ("ext4: allow readdir()'s of large empty directories to be interrupted")
... and why the Hell should an empty directory stay "large"? Something should be done about THAT. There should be some mechanism to shrink them when large size is no longer needed to store directory entries.
I always found that so stupid (and I don't think this is Linux/ext* fs specific). Some years ago, on a RHEL+Plesk server I was looking after (primary role was a busy vbulletin/vbportal site) php session files were piling up to the point that it used up all the inodes on the filesystem. I dutifully stopped the web server, renamed the directory, put down a new one and then proceeded to delete the old one. I couldn't do it, the directory file was so large (~990 Mb) the command was hanging. So I proceeded to delete the files by wildcards (from above it, without entering), in increments to avoid hangs/OOM. Got them deleted, and got the inodes back, but the directory did not shrink and I couldn't delete it. It remained there, for all time, for the lifetime of the server. Forced e2fsck wasn't fixing it, as far as it knew there was nothing wrong with it. No big deal, I removed permissions so nothing could read or traverse it, but it pissed me off.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,086
Original Poster
Rep:
Year 2020, Round 30
Another batch of kernel updates has been scheduled for release on Wednesday, 06 May 2020, at approximately 17:00, GMT. If no problems are found while testing the release candidates, they might be available late Tuesday or early Wednesday (depending on your time zone).
There will be 73 patches in the 5.6.11 update, 57 in 5.4.39, 37 in 4.19.121, 26 in 4.14.179, 18 in 4.9.222 and, finally, 18 patches in the 4.4.222 update.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,086
Original Poster
Rep:
Year 2020, Round 31
Another batch of kernel updates has been scheduled for release on Sunday, 10 May 2020, at approximately 12:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Saturday (depending on your time zone).
There will be 49 patches in the 5.6.12 update, 50 in 5.4.40, 32 in 4.19.122, 22 in 4.14.180, 18 in 4.9.223 and, finally, 312 patches in the 4.4.223 update.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.