Date: Tue, 24 Jan 2017 13:41:38 +0000 From: bugzilla-noreply@freebsd.org To: emulation@FreeBSD.org Subject: maintainer-feedback requested: [Bug 216432] devel/linux-c7-devtools: update kernel-headers to 3.10.0-514.2.2.el7 Message-ID: <bug-216432-4077-x42yyDRIgb@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-216432-4077@https.bugs.freebsd.org/bugzilla/> References: <bug-216432-4077@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Piotr Kubaj <pkubaj@anongoth.pl> has reassigned Bugzilla Automation <bugzilla@FreeBSD.org>'s request for maintainer-feedback to emulation@FreeBSD.org: Bug 216432: devel/linux-c7-devtools: update kernel-headers to 3.10.0-514.2.2.el7 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216432 --- Description --- Created attachment 179274 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D179274&action= =3Dedit patch This patch updates kernel-headers to 3.10.0-514.2.2.el7. The port builds fine on Poudriere on 10.3. Changelog: These updated kernel packages include numerous bug fixes and enhancements, = some of which you can see below. Space precludes documenting all of these bug fi= xes and enhancements in this advisory. To see the complete list of bug fixes and enhancements, users are directed to the related Knowledge Article: https://access.redhat.com/articles/2780461 This update also fixes the following bugs: * Previously, using a floating IP address inside a network namespace in some cases failed with the following error message: "bind: Cannot assign request= ed address". With this update, the kernel respects setting of the net.ipv4.ip_nonlocal_bind parameter to 1 in namespaces, and the floating IP address is now assigned as expected. (BZ#1388591) * In the OpenStack Platform (OSP) environment with multiple guests on the s= ame network, "no route to host" errors occurred when attempting to ping all the guests from a single virtual machine. With this update, the deffering polic= y of the Open vSwitch data path has been fixed, and the described error no longer occurs. (BZ#1388592) * Red Hat Enterprise Linux in some cases failed to boot on platforms due to High Performance Event Timer (HPET) clock access contention. On systems with a T= ime Stamp Counter (TSC) clock and an HPET, the HPET is used to calibrate the TS= C. On some large CPU count systems, this in some cases led to access contention on HPET, which caused a system lockup followed by Nonmaskable Interrupt (NMI) softlockup watchdog. This update reduces HPET counter read contention, thus fixing this bug. As a result, Red Hat Enterprise Linux now boots as expecte= d on affected platforms. (BZ#1388597) * Previously, when two NFS shares with different security settings were mounted, the I/O operations to the kerberos-authenticated mount caused the RPC_CRED_KEY_EXPIRE_SOON parameter to be set, but the parameter was not uns= et when performing the I/O operations on the sec=3Dsys mount. Consequently, wr= ites to both NFS shares had the same parameters, regardless of their security setti= ngs. This update fixes this problem by moving the NO_CRKEY_TIMEOUT parameter to = the auth->au_flags field. As a result, NFS shares with different security setti= ngs are now handled as expected. (BZ#1388604) * Due to an incorrect value in the virtual time base (VTB) register, the ke= rnel of an IBM POWER8 KVM guest in some cases incorrectly detected a soft lockup condition, logged a call trace, and reported the following error: "NMI watchdog: BUG: soft lockup - CPU#x stuck for XXs". This update applies a set of patch= es to fix these problems. As a result, the soft lockups and error messages no lon= ger occur in the described situation. (BZ#1388997) * Previously, a packet loss occurred on transmit when Red Hat Enterprise Li= nux had complex network configuration and was running as a guest on a Xen hypervisor. An upstream patch has been backported that fix the xen-netfront driver to avoid packet loss when ethernet header crosses page boundary. As a result, the packet loss no longer occurs in the described scenario. (BZ#1390257) * After migration to Red Hat Enterprise Linux 7.3, the Unified Extensible Firmware Interface (UEFI) boot failed due to a bug that prevented the kernel from booting through the PE/COFF image entry, which is used by the Extensib= le Firmware Interface (EFI) ipxe boot loader. This update fixes the alignment parameter on the call to the efi_low_alloc() function, and the kernel now b= oots as expected. (BZ#1392044)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-216432-4077-x42yyDRIgb>