Add linux 5.10.47 #2163
Merged
Add linux 5.10.47 #2163
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Create bee file with
cp linux-5.10.24-375.bee linux-5.10.47-390.bee
Update patches to new revisions, which apply cleanly. No functional changes.
Resolves #2150 According to [1] the following parameters are required: VIRTIO, VIRTIO_FS, DAX, FS_DAX, DAX_DRIVER, ZONE_DEVICE. VIRTIO is already selected (as y) by the existing VIRTIO_PCI (=y). Set VIRTIO_FS. DAX is selected by DAX_DRIVER and DAX_DRIVER is selected by BLK_DEV_PMEM && LIBNVDIMM. BLK_DEV_PMEM ist default LIBNVDIMM. Set LIBNVDIMM. Set FS_DAX. DAX_DRIVER is already selected by BLK_DEV_PMEM and LIBNVDIMM. ZONE_DEVICE depends on MEMORY_HOTPLUG and MEMORY_HOTREMOVE. Set all three. [1]: https://virtio-fs.gitlab.io/howto-qemu.html
Create bee file with
cp nvidia_linux-5.10.24-375-460.39-0.bee nvidia_linux-5.10.47-390-460.39-0.bee
|
LGTM |
|
Needs to be tested on a nvidia-workstation. |
|
On sigill: Blender, rstudio, stellarium work as usual. |
|
Thanks a lot.... I'll go for claptrap then.... :-) |
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Latest 5.10 LZT release.
Our current 5.10 kernel ( 5.10.22 and 5.10.24 ) are both vulnerable to an attack from within a kvm guest on amd cpus 1. The bug is fixed in 5.10.28. As we allow our users to use kvm based virtualization ( /dev/kvm is 0666) we should fix that. The risk is not very high, because only our internal users could abuse that and the published exploit needed to be updated to our environment. Anyway, go for latest and greatest.