| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/7734
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/7785
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
| |
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/7770
|
|
|
|
|
|
|
|
| |
Thanks to Arfrever for pointing this out!
Closes: https://bugs.gentoo.org/646702
Bug: https://bugs.gentoo.org/631624#c2
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
|
| |
commit to stable
Package-Manager: Portage-2.3.28, Repoman-2.3.9
RepoMan-Options: --force
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
| |
* desnappify
* fix ARM performance issue. Thanks to David Flogeras and Alexander Tsoy.
Closes: https://bugs.gentoo.org/647952
Closes: https://bugs.gentoo.org/651602
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/650068
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/647784
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
| |
Closes: https://bugs.gentoo.org/649142
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/651866
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/651090
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/644614
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/7686
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/7698
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
| |
This reverts commit 289a2b775c75dd1e88aa972642624a0bf692e957.
|
|
|
|
| |
This reverts commit 2fc1bc6c7b1f41a3a7df74ce8e170996eb7e36d9.
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The device node /dev/vfio/vfio gets created on modprobing the vfio*
modules. This happens in particular on demand when a qemu vm with PCI
passthrough is started up. The default permissios for the freshly
created device node is
crw-rw-rw- 1 root root 10, 196 Mar 27 08:44 /dev/vfio/vfio
This is terrible.
This patch adds an udev rules and makes sure that the device node has rw
permissions for user root, and group kvm (and no permissions for all).
This fixes
- startup when a qemu-kvm is started as non-root (provided the user is
in group kvm, which is our current policy for accessing /dev/kvm, etc.,
anyway).
- work around this security vulnerability, where /dev/vfio/vfio is
created with world writable permissions upon modprobe. [1]
Thanks to username234, Kash Pande, Ted Rodgers for discovery and patch!
[1] Steps to reproduce:
% ls -la /dev/vfio/vfio
crw------- 1 root root 10, 196 Mar 27 15:40 /dev/vfio/vfio
% modprobe vfio
% ls -la /dev/vfio/vfio
crw-rw-rw- 1 root root 10, 196 Mar 27 15:41 /dev/vfio/vfio
[2] I cannot find an udev rule installed by libvirt/qemu/... that
triggers these permissions.
Bug: https://bugs.gentoo.org/651668
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --force
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --force
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/7594
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/7596
|
|
|
|
|
|
|
|
|
|
|
|
| |
With upstream commit of bd891eb380cdf771f0296a39193614a10749088b
virt-manager is strictly python3 only. Update the ebuild to
follow this change.
Closes: https://bugs.gentoo.org/650790
Closes: https://bugs.gentoo.org/647376
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
|
|
|
|
|
|
|
|
| |
* use printf instead of echo -n
* remove dyanmically created directories
Closes: https://bugs.gentoo.org/651296
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
| |
to runc
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|