The news broke recently that in the repository in which the kernel release of Linux 5.19 has received another set of changes related to the DRM subsystem (Direct Rendering Manager) and graphics drivers.
The patch set accepted is interesting because it includes 495k lines of code, which is comparable to the total size of changes in each kernel branch (for example, 506k lines of code were added in kernel 5.17).
hello linus
This is the main drm pull request for 5.19-rc1.
Usual summary below, Intel has enabled DG2 on certain laptop SKUs,
AMD has started new GPU support, msm has user assigned VA controls.Conflicts:
I merged with your tree here a few hours ago, there were two i915 conflicts
but they were pretty easy to solve so I think you can handle them.There aren't many things outside of my realm here.
As usual let me know if there is any problem,
It is mentioned that in the received patch approximately 400 lines included aggregated come from ASIC register data header files automatically generated in the AMD GPU driver.
In addition to this, it is also highlighted that another 22,5 thousand lines provide the initial implementation of AMD SoC21 support. The total size of the AMD GPU driver exceeded 4 million lines of code (for comparison, the entire Linux 1.0 kernel included 176 thousand lines of code, 2,0 – 778 thousand, 2,4 – 3,4 million, 5,13 – 29,2 million). In addition to SoC21, the AMD driver includes support for SMU 13.x (System Management Unit), updated support for USB-C and GPUVM, and is ready to support the next generation of RDNA3 (RX 7000) and CDNA (AMD instinct).
In the Intel driver, the most changes (5,6 thousand) is in the power management code. Also added Intel driver IDs for Intel DG2 (Arc Alchemist) GPUs used in laptops, provided initial support for the Intel Raptor Platform Lake-P (RPL-P), added information about Arctic Sound-M graphics cards, implemented ABI for compute engines, added Tile4 format support for DG2 cards, implemented DisplayPort HDR support for systems based on the Haswell microarchitecture.
While on the part of the nouveau controller, total, the changes affected about a hundred lines of code (change was made to use drm_gem_plane_helper_prepare_fb driver, applied static memory allocation for some structures and variables). As for the use of open source Nouveau kernel modules by NVIDIA, the work so far has been reduced to identifying and removing bugs. In the future, it is planned to use the released firmware to improve the performance of the controller.
If you want to know more about the changes proposed for the next version of Linux 5.19, you can consult the details in the following link
Last but not least, It is also worth mentioning that a vulnerability was recently identified (CVE-2022-1729) in the Linux kernel that could allow a local user to gain root access to the system.
Vulnerability is caused by a race condition in the perf subsystem, which can be used to initiate access to an already freed area of kernel memory (use-after-free). The problem has been manifest since the release of kernel 4.0-rc1. Exploitability has been confirmed for versions 5.4.193+.
this is an announcement of a recently reported vulnerability (CVE-2022-1729) in the perf subsystem of the Linux kernel. The problem is a race condition that was shown to allow a local privilege of escalation to root on current kernel version >= 5.4.193, but the bug seems to exist from the kernel version 4.0-rc1 (the patch fixes the commit of this version).
Fortunately, major Linux distributions often restrict the use of perf for non-privileged users by setting the sysctl variable kernel.perf_event_paranoid >= 3, effectively representing the harmless vulnerability.
The fix is currently only available as a patch. The danger of the vulnerability is mitigated by the fact that most distributions restrict access to perf to non-privileged users by default. As a security fix, you can set the sysctl kernel.perf_event_paranoid parameter to 3.