The 5.13 kernel has been released
Of course, if the last week was small and calm, 5.13 overall is actually fairly large. In fact, it's one of the bigger 5.x releases, with over 16k commits (over 17k if you count merges), from over 2k developers. But it's a 'big all over' kind of thing, not something particular that stands out as particularly unusual.
Headline features in this release include
the "misc" group controller,
multiple
sources for trusted keys,
kernel
stack randomization on every system call,
support for Clang control-flow integrity
enforcement,
the ability to call kernel functions
directly from BPF programs,
minor-fault
handling for userfaultfd(),
the removal of /dev/kmem,
the Landlock security module,
and, of course, thousands of cleanups and fixes.
(Log in to post comments)
The 5.13 kernel has been released
Posted Jun 28, 2021 13:58 UTC (Mon) by jkingweb (subscriber, #113039) [Link]
The 5.13 kernel has been released
Posted Jun 28, 2021 23:32 UTC (Mon) by pabs (subscriber, #43278) [Link]
https://www.kernel.org/doc/html/latest/process/stable-ker...
The 5.13 kernel has been released
Posted Jun 29, 2021 16:01 UTC (Tue) by jkingweb (subscriber, #113039) [Link]
https://github.com/thesofproject/linux/issues/2700#issuec...
... which referred to two patches and mentioned the fixes would land in 5.13—and after trying 5.13rc6 this morning, I was indeed graced with sound.
The 5.13 kernel has been released
Posted Jun 30, 2021 0:06 UTC (Wed) by pabs (subscriber, #43278) [Link]
It is relatively simple; since this is a patch that has already been merged, you should choose option 2:Option 2 After the patch has been merged to Linus’ tree, send an email to stable@vger.kernel.org containing the subject of the patch, the commit ID, why you think it should be applied, and what kernel version you wish it to be applied to.
The hard part is identifying which commit fixed the issue, but a comment on the issue points out a list of 10 commits that fix the issue for someone else using Linux 5.11.