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.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,014
Rep:
Quote:
Originally Posted by marav
Probably because they don't have bug report and they didn't face the problem
Plus the fact that I have no trace of any bug in the logs
That was not my question: I wonder how come that I noticed the issue with pretty light computer use while kernel developers who use linux heavily did not. This sort of bug should be pretty visible for someone constantly accessing disk and cpu, n'est-ce pas?
@Petri Kaukasoina
I don't think kernel that I would recompile 6.2.1 to get 6.2.1
6.x series are exactly the same kernel when I look at the config.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,163
Original Poster
Rep:
Quote:
Linux Inadvertently Has Been Leaving IBRS-Mitigated Systems Without STIBP
Michael Larabel. 27 February 2023.
The Linux kernel since last year has mistakenly left systems relying on the original Indirect Branch Restricted Speculation (IBRS) for Spectre V2 mitigation without Single Threaded Indirect Branch Predictor (STIBP) coverage for cross-HyperThread dealing with this Spectre vulnerability. There is a patch underway that is resolving this issue for Intel Skylake era systems..........
EXT4 Scores A Nice Direct I/O Performance Improvement With Linux 6.3
Code:
With the EXT4 file-system being quite mature at this stage, with many kernel cycles these days
this widely-used file-system just sees bug fixes and other minor work. But for the newly-opened
Linux 6.3 cycle, EXT4 is seeing a nice performance boost under certain conditions with direct I/O.
Hard lock-up with no error messages after the bootloader (elilo) gets started on 6.2, 6.1.14 is fine. Glad I always keep that Last Known Good kernel around. x86_64 AMD Ryzen 5, Radeon Oland
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,163
Original Poster
Rep:
Year 2023, Round 13.
Another batch of updates has been scheduled for release on Friday, 3 March 2023, at approximately 18:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Thursday (depending on your time zone).
io_uring: ensure that io_init_req() passes in the right issue_flags
We can't use 0 here, as io_init_req() is always invoked with the
ctx uring_lock held. Newer kernels have IO_URING_F_UNLOCKED for this,
but previously we used IO_URING_F_NONBLOCK to indicate this as well.
Generic Kernel Version 6.1.15.kjh is running fine on my Slackware64 15.0 + Multilib LapTop.
No CVE References were found for 6.2.2, 6.1.15, 5.15.98, 5.10.172, 5.4.234 or 4.19.275, but as always, do check the ChangeLogs for other security-related fixes.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,163
Original Poster
Rep:
Quote:
Intel Continues With More Big-Time Optimizations To The Linux Kernel
By Michael Larabel. 6 March 2023.
............Intel engineers have been sorting through a bottleneck within the Linux kernel networking code and discovered a performance issue around concurrency with the dst_entry data structure..............
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,163
Original Poster
Rep:
Year 2023, Round 14.
Another batch of updates has been scheduled for release on Thursday, 9 March 2023, at approximately 17:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Wednesday (depending on your time zone).
The details:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
