6,534
edits
Changes
m
** vethX interfaces of OpenVZ and VZ containers are not affected as they use a different driver. The affected veth driver was used inside Docker-ready containers or could be used by host admin for their own purposes.
minor formatting fix
* NFS client with kernels 2.6.32-573.10.2.el6 or above could hang with 'not responding, still trying' messages and running processes in spinlock. (https://access.redhat.com/solutions/2215491)
* Network devices that used the mainline veth driver did not check TCP checksums. (https://access.redhat.com/solutions/2216661)
* Warning at drivers/block/ploop/io_direct_map.c:841 trim_extent_mappings. (PSBM-45999)
* LDT entries were incorrectly restored from CPT image. (OVZ-6228)
