-
PSBM-102848
(enhancement) ploop: added interface to dump the cached BAT.
It was discovered that containers could get a broken on-disk BAT but have healthy in-kernel data in certain cases. To detect and fix such conditions, the means to dump the cached BAT were implemented in ploop. Note that, to make use of this enhancement, version 7.0.187.4 or newer of the userspace ploop tools is needed.
-
PSBM-102655
netfilter: kernel crash in the implementation of nf_tables due to use-after-free in dynamic operations.
-
PSBM-102363
A container with NFS server could force other such containers to use the older NFSv4 client tracker, which slows down NFS mounts.
-
VSTOR-32221
mpt2sas: scheduling while atomic in _scsih_io_done().
-
PSBM-101823
ploop: potential corruption of the index during discard operation.
A race condition was discovered in ploop, which could lead to corruption of the index during discard operations in certain cases. Note. It is not recommended to manually unload the ReadyKernel patch with the fix for this issue while any discard operations for ploop images are in progress: the ploop images could be corrupted as a result. Upgrading the patch is OK, only manual unloads and downgrades can be problematic.
-
PSBM-102070
ploop: warn if a discard request is issued for the ploop header.
-
PSBM-102033
ve: detect removal of additional system libraries in the containers to simplify debugging.
-
PSBM-101783
Potential leak of a reference counter for a memory cgroup in memcg_expand_shrinker_maps().
-
PSBM-101533
Potential corruption of ploop images due to a race between the truncation thread and resize operations.
-
PSBM-101595
ve: make it easier to analyze removal of system libraries in the containers.
-
CVE-2019-15538
xfs: potential denial of service caused by missing unlock operation in xfs_setattr_nonsize().
It was discovered that xfs_setattr_nonsize() would not unlock 'ILOCK' lock if the user or group were out of their disk quota. As a result, any subsequent operation, which needed to take 'ILOCK', would get stuck, leading to a denial of service.
https://access.redhat.com/security/cve/cve-2019-15538
-
PSBM-101492
nf_tables: kernel crash in nft_rbtree_lookup().
-
PSBM-101189
ploop: holes in raw ploop images were handled incorrectly.
-
PSBM-94695
Kernel crash due to out-of-bounds memory accesses in process_vm_readv().
It was discovered that the implementation of process_vm_readv() system call could try to access memory outside of the structures it was processing in certain cases. A local unprivileged user could use this vulnerability to crash the system.
-
PSBM-101159
quotaoff operation executed in a container could get stuck in D state.
-
PSBM-101143
Certain operations with an empty ploop image could lead to its unexpected growth.
-
PSBM-101249
Incomplete fix for PSBM-100575: reading of /proc/bc/resources line by line would never end.
-
PSBM-100509
memcg: memory corruption caused by writing beyond the end of shrinker_map structure.
-
PSBM-100722
ixgbe: lots of warnings in the system log due to incorrect check for firmware errors.
-
PSBM-100739
ploop: kernel crashes when processing discard requests for ploop images in raw format.
-
PSBM-100118
scsi: printing lots of messages about rejected I/O causes a hard lockup and a kernel crash.
-
PSBM-100593
Kernel crash in shrink_slab() when trying to mount an image with a broken ext4 file system.
-
PSBM-100575
Reading of /proc/bc/resources line by line would never end: no end of file was reported.
-
PSBM-100579
Potential kernel crash in __radix_tree_insert() when fscache is used for NFS mounts.
-
PSBM-99764
sunrpc: potential kernel crash in bc_svc_process().
-
PSBM-100441
A bug in ploop prevented recovery of corrupted ploop images.
-
VSTOR-29472
The minimum amount of reserved free memory (vm.min_free_kbytes) was set too high by default.
-
PSBM-96262
kvm: potential system hang due to an error in mmu_shrink_scan().
-
PSBM-96057
Processes could get stuck in copy_net_ns() forever.
