[Info] Linux 5.15 released

Linux 5.15 with fresh NTFS driver and SMB server

The new kernel facilitates data exchange with Windows with a stable and secure NTFS driver. It also includes the SMB server in the kernel.

In the night from Sunday to Monday, Linus Torvalds has released the Linux kernel in version 5.15. The new version is not just a maintenance release, but brings new features. Especially for cross-platform data exchange with other systems, the release offers a rich plus in the form of a new NTFS driver. Other important innovations: Samba in the kernel and optimizations in the file system area. In the following, we take a brief look at the highlights in Linux 5.15.

Stable NTFS thanks to Paragon driver

Paragon Software GmbH has contributed a driver for the NTFS file system in Linux 5.15. It replaces the old kernel NTFS driver. Since this only controlled read access, most users had previously relied on the FUSE driver (Filesystem in USErspace) NTFS-3G. However, its incompletely implemented NTFS specification could leave file systems damaged in crashes.

The new driver fully implements NTFS in version 3.1. This also includes the journal replay, which can restore the file system as far as possible in the event of a crash. Paragon intends to maintain the driver in the Linux kernel in the future. New features are already planned for the next Linux versions.

We had already dedicated a longer report to Paragon’s NTFS3 driver in September shortly after its integration into the kernel:

KSMBD: Samba in the kernel

With KSMBD, Linux 5.15 introduces a new module that moves the SMB3 protocol into the kernel. The SMB (Server Message Block) or CIFS (Commin Internet File System) protocol has so far been the domain of Samba under Linux. With the new kernel module, the kernel developers are creating an optimized SMB server, which will be trimmed for performance and data throughput. It is not supposed to be a competitor to Samba, but a supplement.

KSMBD only provides the server; clients are reserved for Samba. In addition, KSMBD only speaks SMB version 3; clients with earlier SMB versions cannot connect to the kernel SMB. Likewise, old insecure authentication protocols like NTLMv1 are left out. This creates a lean server, which in the future - due to its proximity to the hardware in the kernel - should bring more features to Linux. For example, “SMB Direct” is at the top of the agenda for future enhancements. It is supposed to increase the performance of the SMB server considerably.

KSMBD aims at high data throughput. Samba, on the other hand, is broadly and openly positioned and scores with the tools, the various security services and the connection to LDAP and Active Directory.

File systems optimized

Linux 5.15 has made significant improvements to the file systems. Ext4 shines with faster handling of orphan files and also increases performance from the delalloc write buffer.

XFS has also seen performance improvements. In addition, the file system can now handle data beyond the year 2038. This “feature” was already available, but was previously classified as “experimental”. Now it is considered stable for productive use. Another novelty in XFS: As of now, it is no longer possible to switch off the so-called quota accounting. Although the corresponding enforcement can be shut down, the “accounting” now continues to run in the background - albeit without consequences. Reason for this solution were not comprehensible crashes when switching off the quotas.

btfs follows suit with the so-called ID-Mapped Mounts, which we had discussed in detail in our Linux 5.12 release. In addition, it can now handle fs-verify, a generic layer for transparent integrity and authenticity protection of read-only files. This brings it in line with ext2 and F2FS, which have offered this feature for some time.

Other new features and even more kernel details

Linux 5.15 removes the LightNVM subsystem, considered obsolete and replaced by newer NVMe (Non-Volatile Memory Express) standards, which previously allowed direct access to SSDs without an emulation layer. The support for Apple’s M1 was further expanded with Linux 5.15, but is not yet considered production stable.

Furthermore, the data access monitor DAMON was included in the kernel. And also in the memory management Linux 5.15 brings innovations: It introduces the system call process_mrelease(). cgroup receives support for SCHED_IDLE. SCHED_IDLE tasks run only if no other tasks are ready for execution. However, within cgroup, the associated tasks retain their weights.

Translated with www.DeepL.com/Translator (free version)

German source:


5.15 will also be an LTS kernel.


That’s good news. I was running 5.14 on all machines but ended up going back to 5.10 LTS because of issues on some of them. It makes no difference in my use case. New is nice but stability is more important to me. For now I’ll stick with 5.10 and see how 5.15 evolves :grin:

1 Like

Just keep in mind that some time soon linux-lts will automatically become 5.15. There is an unfortunate period where linux-lts and linux are basically the same.


Yep for sure, although there are ways around that! I’m happy to try the next LTS.

juste missing io-uring optimization & HDMI /DP 2.0 ( theses features will be in 5.16 version )

1 Like

runs fine here :slight_smile:

I was guessing so but wasn’t sure. From what you wrote EOS will update from 5.10 to 5.15 automatically? No manual switching needed?

kernel naming is simple and kiss… it goes when it goes. :slight_smile: its not like manjaro :slight_smile:

1 Like

Correct. There is no manual switching needed for any standard Arch kernel.

1 Like

Yes. If you run linux-lts it will switch automatically from 5.10 to 5.15

1 Like

And 5.10 should be added to the kernel-lts repo for those who still prefer / require 5.10.


I think you can still get 4.19 if required although I haven’t checked this. There is no reason “legacy” things should not be available to those who want them. They take up little space. Let us not forget our history, it is how we arrived here!

1 Like

All lts kernels still maintained on kernel.org are available …

$ pacman -Sl kernel-lts
kernel-lts haveged 1.9.14-1
kernel-lts lib32-nvidia-390xx-utils 390.144-1
kernel-lts lib32-nvidia-470xx-utils 470.82.00-2
kernel-lts lib32-opencl-nvidia-390xx 390.144-1
kernel-lts lib32-opencl-nvidia-470xx 470.82.00-1
kernel-lts libxnvctrl-390xx 390.144-1
kernel-lts libxnvctrl-470xx 470.82.00-1
kernel-lts linux-lts414 4.14.253-1
kernel-lts linux-lts414-docs 4.14.253-1
kernel-lts linux-lts414-headers 4.14.253-1
kernel-lts linux-lts419 4.19.214-1
kernel-lts linux-lts419-docs 4.19.214-1
kernel-lts linux-lts419-headers 4.19.214-1
kernel-lts linux-lts44 4.4.290-1
kernel-lts linux-lts44-docs 4.4.290-1
kernel-lts linux-lts44-headers 4.4.290-1
kernel-lts linux-lts49 4.9.288-1
kernel-lts linux-lts49-docs 4.9.288-1
kernel-lts linux-lts49-headers 4.9.288-1
kernel-lts linux-lts510 5.10.76-1
kernel-lts linux-lts510-docs 5.10.76-1
kernel-lts linux-lts510-headers 5.10.76-1
kernel-lts linux-lts54 5.4.156-1
kernel-lts linux-lts54-docs 5.4.156-1
kernel-lts linux-lts54-headers 5.4.156-1
kernel-lts nvidia-390xx-dkms 390.144-2
kernel-lts nvidia-390xx-settings 390.144-1
kernel-lts nvidia-390xx-utils 390.144-1
kernel-lts nvidia-470xx-dkms 470.82.00-1
kernel-lts nvidia-470xx-settings 470.82.00-1
kernel-lts nvidia-470xx-utils 470.82.00-2
kernel-lts opencl-nvidia-390xx 390.144-1
kernel-lts opencl-nvidia-470xx 470.82.00-1

5.10 just added too … @jonathon got it covered even before 5.15 hits testing.

Arch users should have this repo enabled IMHO … I would argue that EOS next ISO should have this enabled by default also. Could help also with installing the correct nvidia driver during installation, with 390 and 470 binaries available.


Yeah, you most certainly can, and it still works fine.

The easiest way to install it is this:

It would be nice if it could be made as an option in Calamares, but I don’t think it should be included by default on every install. Most people won’t need this, and for them this will just slow down db synching on every update (not to mention, generate unnecessary traffic towards @jonathon’s mirrors). However for those who do need legacy kernels and drivers, this repo is very convenient.

1 Like

@otherbarry @Kresimir Thanks for the info. I think it’s good for people to know these things. I don’t think these options should be default however: too many choices could be confusing for a newcomer, and perhaps lead to unwise choices. Maybe an article in EnOS Discover (wiki/knowledge base) might be useful?

1 Like

I couldn’t disagree more with that!

There is no such thing as too much choice. If you think that, you should be using windoze.

I did say “newcomer”! Perhaps not for me, or a Frog :stuck_out_tongue:

Does this mean I can just remove the ntfs-3g package?

We don’t need such newcomers, these are the worst people that exist, mindless zombies who lack free will.