Red Hat ENTERPRISE 5.4 RELEASE NOTES, Manual

Page: 139 / 466

RHSA-2009:0473: Important security and bug fix update
121
• the Linux kernel implementation of the Network File System (NFS) did not properly initialize the file
name limit in the nfs_server data structure. This flaw could possibly lead to a denial of service on a
client mounting an NFS share. (
CVE-2009-1336
825
, Moderate)
This update also fixes the following bugs:
• the enic driver (Cisco 10G Ethernet) did not operate under virtualization. (
BZ#472474
826
)
• network interfaces using the IBM eHEA Ethernet device driver could not be successfully configured
under low-memory conditions. (
BZ#487035
827
)
• bonding with the "arp_validate=3" option may have prevented fail overs. (
BZ#488064
828
)
• when running under virtualization, the acpi-cpufreq module wrote "Domain attempted WRMSR"
errors to the dmesg log. (
BZ#488928
829
)
• NFS clients may have experienced deadlocks during unmount. (
BZ#488929
830
)
• the ixgbe driver double counted the number of received bytes and packets. (
BZ#489459
831
)
• the Wacom Intuos3 Lens Cursor device did not work correctly with the Wacom Intuos3 12x12 tablet.
(
BZ#489460
832
)
• on the Itanium® architecture, nanosleep() caused commands which used it, such as sleep and
usleep, to sleep for one second more than expected. (
BZ#490434
833
)
• a panic and corruption of slab cache data structures occurred on 64-bit PowerPC systems when
clvmd was running. (
BZ#491677
834
)
• the NONSTOP_TSC feature did not perform correctly on the Intel® microarchitecture (Nehalem)
when running in 32-bit mode. (
BZ#493356
835
)
• keyboards may not have functioned on IBM eServer System p machines after a certain point during
installation or afterward. (
BZ#494293
836
)
• using Device Mapper Multipathing with the qla2xxx driver resulted in frequent path failures.
(
BZ#495635
837
)
• if the hypervisor was booted with the dom0_max_vcpus parameter set to less than the actual
number of CPUs in the system, and the cpuspeed service was started, the hypervisor could crash.
(
BZ#495931
838
)
• using Openswan to provide an IPsec virtual private network eventually resulted in a CPU soft lockup
and a system crash. (
BZ#496044
839
)
• it was possible for posix_locks_deadlock() to enter an infinite loop (under the BKL), causing a
system hang. (
BZ#496842
840
)
Users should upgrade to these updated packages, which contain backported patches to correct these
issues. The system must be rebooted for this update to take effect.