Menu Close
Red Hat Training
A Red Hat training course is available for Red Hat Enterprise Linux
5.5 Technical Notes
Detailed notes on the changes implemented in Red Hat Enterprise Linux 5.5
Edition 5
Red Hat Inc.
Abstract
Preface
Chapter 1. Package Updates
1.1. acl
1.1.1. RHBA-2009:1652: bug fix update
Note
1.2. acpid
1.2.1. RHBA-2010:0004: bug fix update
Note
1.2.2. RHSA-2009:1642: Important security update
Important
1.3. aide
1.3.1. RHBA-2010:0036: bug fix update
Note
1.4. anaconda
1.4.1. RHBA-2010:0194: bug fix and enhancement update
- previously, when anaconda could not read the extended display identification data (EDID) of a monitor, it reverted to text mode. However, EDID information is frequently not available on systems connected to Keyboard–Video–Mouse (KVM) switches. Therefore, when installing Red Hat Enterprise Linux 5 on a system with a KVM switch, installation would be constrained to text mode. Anaconda no longer checks for bad or missing EDID, and allows graphical installation to proceed even when this information is unavailable. Graphical installation on machines attached to KVM switches therefore continues as if them monitor were connected directly to the graphics adapter. (BZ#445486)
- previously, anaconda expected storage devices to be available immediately when it probed for the location of a kickstart file. On systems where USB storage might not be available immedately (for example, IBM BladeCenter systems), anaconda would not find the kickstart file and would prompt the user for its location. This interaction negated the usefulness of kickstart, since the installation could not then complete unattended. Anaconda now waits until it has probed five times or for more than 31 seconds before prompting the user for the location of a kickstart file. This allows USB storage enough time to respond and for kickstart to proceed unattended. (BZ#460566)
- previously, some user interface elements in the the Malayalam translation of anaconda overlapped. The overlapping elements disabled some buttons in the screen where anaconda lets users to choose a partitioning scheme for the system, and prevented installation from continuing. The text of the Malayalam translation has been shortened so that the interface elements no longer overlap. The buttons on the partitioning scheme screen now work correctly and allow installation to continue. (BZ#479353)
- during installation, anaconda automatically examines any storage device that has the label
OEMDRV
for driver updates and applies any updates that it finds there. Previously, anaconda searched for this label on the devices listed in/proc/partitions
. However,/proc/partitions
does not identify CD or DVD media, so anaconda overlooked optical disks that had the correct label. Anaconda now examines the devices listed in/sys/block
. Therefore, anaconda correctly identifies CDs and DVDs labelledOEMDRV
as driver discs and automatically applies any driver updates contained on them. (BZ#485060) - previously, if anaconda required network access early in an installation (for example, to retrieve a kickstart file or driver disk image), it temporarily saved information about the network configuration while it enabled access to the network. However, if anaconda required network access again for a separate reason, it would not attempt to configure network access again, but would not be able to connect to the network either, because it no longer retained the configuration information that it had already used. Therefore, anaconda could not download both a kickstart file and a driver disk image over a network. Anaconda now retains the network configuration that it obtains early in the installation process, and can reuse this information multiple times. Therefore, anaconda can use more than one resource obtained over a network during installation. (BZ#495042)
- previously, while upgrading a system, anaconda did not check whether packages marked for installation as dependencies were already installed on the system. Consequently, many packages would be reinstalled during an upgrade, wasting time and, in the case of network installations, bandwidth. Now, when performing an upgrade, anaconda matches the packages to be installed against the packages that are already installed. Any packages with the same Name, Arch, Epoch, Version, Release (NAEVR) as a package already on the system are skipped and not reinstalled. (BZ#495796)
- previously, anaconda did not specify a value for
HOTPLUG
when writing the system's networking configuration files, although it did write a value forONBOOT
. BecauseHOTPLUG
is enabled by default, the effect of disablingONBOOT
was limited because any interface not activated at boot time would be enabled anyway whenever probed by the system. Anaconda now writes a value forHOTPLUG
, setting it to the same value asONBOOT
. Therefore, any network interface not meant to be enabled at boot time will not be automatically enabled by probing either. (BZ#498086) - the
part
kickstart command accepts an option called--label
that allows a label to be applied to a disk partition during a kickstart installation. However, the code that implemented this option was previously missing from anaconda. Any label specified in a kickstart file was therefore ignored. Anaconda now includes code to transfer the specified label from the kickstart file to the disk partition. Users can now label disk partitions during kickstart installations. (BZ#498856) - when running in rescue mode, anaconda previously lacked the ability to identify partitions on logical volumes if the partitions were identified in
fstab
by label rather than by device name. Therefore, if the root (/
) partition were identified in this way, the usefulness of rescue mode would be limited. Anaconda in rescue mode now uses the getLabels() method to find partitions and therefore properly detects root partition even if it resides on a logical volume and is identified by label infstab
. (BZ#502178) - previously, the help text available while configuring
NETTYPE
for IBM System z systems did not mention HiperSockets. Users new to System z might therefore not have known to chooseqeth
to configure HiperSocket interfaces on their hardware. The help text has now been updated to indicate the correct choice and users can select the appropriate option. (BZ#511962) - when the
RUNKS
was set to0
in theCMSCONFFILE
file on IBM System z systems, anaconda should have performed an installation in interactive mode. However, a rewrite of linuxrc.s390 changed the behavior of RUNKS and led to anaconda ignoring this variable. Installation would therefore proceed in non-interactive mode regardless of what value was set inCMSCONFFILE
. A new test is now included in the version of linuxrc.s390 in Red Hat Enterprise Linux 5.5 so that anaconda honorsRUNKS=0
and performs an interactive install if this value is set. (BZ#513951) - by design, anaconda recognizes any block device with the label
OEMDRV
as a driver disc and searches it for a driver update. However, anaconda previously failed to examinedev
nodes and therefore, it would not recognize this label on USB storage devices mounted as a partitionless block devices. Anaconda now examinesdev
nodes for the labelOEMDRV
and treats them the same as partitions with this label. It is therefore possible to use a partitionless device as a driver disc. (BZ#515437) - previously, anaconda did not reinitialize its record of the partition layout on a system when users clicked the back button from the partitioning screen. Therefore, when a user selected a partition layout, went back to an earlier screen, and then went forward again to choose a different partition layout, anaconda would attempt to implement the new partition layout over the previously-selected partition layout instead of the partition layout actually present on the system. This would sometimes result in a crash. Now, when users step backwards from the partitioning screen. anaconda reinitializes its record of the partitions present on the system. Users can therefore change their minds about partitioning options without crashing anaconda. (BZ#516715)
- systems store information about iSCSI targets to which they are connected in the iSCSI Boot Firmware Table (iBFT) in BIOS. Previously, however, when anaconda installed Red Hat Enterprise Linux 5 from a local installation source such as a CD, DVD, or hard disk, it would not initialize network connections before asking users to configure storage on the system. Therefore, on systems with iSCSI storage, users would have to configure a network connection manually before proceding with installation, even when this information was already available to anaconda in the system BIOS. Now, when anaconda detects a valid iBFT present on a system, it automatically loads the network configuration specified there and does not requre users to enter this information. Installation from local media on systems with iSCSI storage is therefore simpler and more reliable. (BZ#517768)
- due to faulty logic, anaconda previously did not parse IPv6 addresses correctly and attempted to read the final byte of the address as a port number. It was therefore not possible, for example, to install on an iSCSI target specified by in IPv6 address. The logic by which anaconda parses IP addresses has now been corrected, but now requires IPv6 addresses to be specified in the
[address]:port
form to comply with the relevant RFCs. This form removes ambiguity, since IPv6 addresses are still valid if they omit a sequence of bytes with zero values. When IPv6 addresses are specified in this format, anaconda parses them correctly and installation continues as normal. (BZ#525054) - comments in kickstart files are marked with a pound symbol (
#
) at the start of the line. However, anaconda did not previously account for the possibility that users might mark a comment with multiple pound symbols (for example,#####
). Anaconda would therefore attempt to parse lines that started with multiple pound symbols and installation would fail. Anaconda now recognizes lines that start with multiple pound symbols as comments and does not attempt to parse them. Users can now safely mark comments in kickstart files in this way. (BZ#525676) - to avoid a circular dependency that exists between the ghostscript and ghostscript-fonts packages, anaconda ignored ghostscript's dependency on ghostscript-fonts. However, ghostscript-fonts was not explicitly installed as part of the Printing package group. The usefulness of Ghostscript as installed by anaconda was therefore limited. Anaconda still avoids the circular dependency, but now specifically installs ghostscript-fonts when users select the Printing package group. (BZ#530548)
- previously, anaconda did not automatically instruct the kernel to check for multipath devices when installing on IBM System z systems. Therefore, unless users booted with the
mpath
boot option, iSCSI devices detected on more than one path would be represented in the installer multiple times, one for each path. Anaconda now automatically loads thempath
boot option and therefore represents multipath devices correctly. (BZ#538129) - Dell PowerEdge servers equipped with the SAS6i/R integrated RAID controller use BIOS Enhanced Disk Drive Services (EDD) to identify the storage device from which to boot the operating system. Previously, anaconda did not parse EDD to identify the correct boot device. Consequently, with a RAID 0 and RAID 1 configured on the system, anaconda would choose the wrong device and the system would not be bootable. Anaconda now parses EDD to support the SAS6i/R integrated RAID controller, so that it selects the correct boot device for systems that use this device. (BZ#540637)
- previously, anaconda would always attempt to reconstruct pre-existing Logical Volume Management (LVM) devices during installation. Anaconda would attempt to recreate the LVM device even when a user cleared the LVM partitions from one or more of the disks that held partitions that formed part of a volume group. In this case, installation would fail. Now, anaconda no longer attempts to reconstruct incomplete LVM devices. Users can therefore safely re-allocate storage that was once part of a volume group and installation will proceed as expected. (BZ#545869)
- when
ksdevice=link
is set in a kickstart file, anaconda should automatically select the first available network interface and use it during installation. This avoids the need for user input and allows installation to proceed unattended. However, if interfaces were in a state where anaconda could not determine their status, anaconda would revert to interactive more and prompt the user to select a network interface, thus making unattended installation impossible on systems where network interfaces could be in such a state. Anaconda now forces the network interfaces on the system intoIFF_UP
andIFF_RUNNING
states before it attempts to obtain link status. Because the interfaces are now in a state where they can report their link status to anaconda, Anaconda can automatically choose one to use during installation and kickstart installations can proceed unattended. (BZ#549751) - previously, when installing on IBM System z systems, anaconda assumed that the network gateway was unreachable if its attempt to ping the gateway timed out after 10 seconds. Anaconda would then prompt the user to select a gateway. However, if
IPADDR
in theconf
file has changed recently, network interfaces take longer to respond. Anaconda now prompts the user only when three pings have failed and therefore avoids prompting the user for gateway information that is already correctly specified in theconf
file. (BZ#506742)
- after transferring installation files to a z/VM guest, a user must execute a series of Conversational Monitor System (CMS) commands to IPL the zLinux installation. These commands can be scripted, but no such script was previously included with Red Hat Enterprise Linux 5. The lack of a readymade script made installation more difficult for users unfamiliar with CMS commands. The CMS script for starting the install process on z/VM is now included in the Red Hat Enterprise Linux 5 images, simplifying installation. (BZ#475343)
- anaconda now loads the Brocade BNA Ethernet Controller driver, and supports Brocade Fibre Channel to PCIe Host Bus Adapters. (BZ#475707)
- previously, anaconda did not offer users the opportunity to configure NFS options during interactive installation (although these could be configured in kickstart files). Users who needed to fine-tune NFS parameters for installation were therefore forced to run an unattended installation. Now, anaconda presents users who select NFS installation with a dialog in which they can configure NFS options to suit their needs. (BZ#493052)
- previously, it was not possible to configure hypervisor parameters during a kickstart installation. As a result, users needed to specify hypervisor parameters manually after installation, negating the usefulness of kickstart as as a mechanism for unattended installations. Now, anaconda recognizes a new kickstart option,
--hvargs
and sets Hypervisor parameters accordingly. (BZ#501438) - previouisly, during a kickstart installation when multiple multipath LUNs were available, anaconda would automatically choose the LUN with the lowest ID number for the root device. Users had no ready way to customize this behavior. Now, anaconda supports a
multipath
kickstart command with--name
and--device
options that allow users to specify a LUN for root. (BZ#502768) - anaconda can retrieve kickstart files from FTP servers. Previously, however, anaconda did not support users specifying authentication credentials to access an FTP server. Therefore, if access to the server were protected by a passphrase, anaconda could not retrieve the kickstart file. Now, when specifying the location of a kickstart file with the
ks=
boot option, users can provide a passphrase to allow anaconda to retrieve the kickstart files fom a protected server. (BZ#505424) - previously, troubleshooting errors that occurred while running %pre and %post kickstart scriptlets was very difficult because anaconda did not log the behavior of these scriptlets. Anaconda now copies %pre and %post kickstart scriptlets to
/tmp
together with a log. These records make troubleshooting kickstart installations easier. (BZ#510636) - Reipl is a kernel feature that instructs IBM System z systems where to boot next, as these systems do not have a default boot location. Anaconda did not previously support Reipl, which meant that during installation, users had to specify a boot location manually between different phases of the installation. Anaconda now supports Reipl, so these reboots can happen automatically. (BZ#512195)
- NPort ID Virtualization (NPIV) presents one physical Fibre Channel adapter port to the SAN as multiple WWNN/WWPN pairs. Anaconda now supports NPIV, which allows users on PowerPC systems to install to a NPIV LUN. (BZ#512237)
- the Python executables that make up anaconda now all explicitly use the system Python (
#! /usr/bin/python
instead of#! /usr/bin/env python
). This ensures that anaconda functions correctly when more than one Python stack is present on a system. (BZ#521337) - anaconda now supports the Emulex OneConnect iSCSI network interface card. (BZ#529442)
- anaconda now supports PMC Sierra MaxRAID controller adapters. (BZ#532777)
- although users have been able to specify package groups for installation in kickstart files, using the
@
prefix, it was not possible to exclude package groups from installation, only individual packages. Anaconda now supports excluding package groups with the-@
prefix (BZ#558516) - anaconda now loads the xorg-x11-qxl-drv and xorg-x11-ast-drv X11 video drivers as required. xorg-x11-qxl-drv supports the qemu QXL video accelerator when installing Red Hat Enterprise Linux 5 as a guest operating system. xorg-x11-ast-drv supports ASPEED Technologies video hardware. (BZ#567666)
1.5. apr-util
1.5.1. RHEA-2010:0310: enhancement update
1.6. at
1.6.1. RHBA-2009:1654: bug fix and enhancement update
Note
1.7. audit
1.7.1. RHBA-2010:0228: bug fix update
1.8. autofs
1.8.1. RHBA-2009:1468: bug fix update
Note
1.8.2. RHBA-2010:0265: bug fix update
- If an included map read failed, autofs returned an error and subsequent master map entries were not read. This update reports the failure in the log but master map reading no longer ceases. (BZ#506034)
- autofs could segfault if it called
xmlCleanupParser
concurrently from multiple threads, as this function is not re-entrant. autofs has been changed to call this function only once from its main thread, when the application exits. (BZ#513289) - autofs could segfault at startup when using LDAP under certain circumstances. autofs would fail to try and retrieve a query dn if:
- LDAP is being used to store autofs maps and...
- The LDAP schema to be used for the maps is explicitly defined in the autofs configuration and...
- No master map entries exist in LDAP.
This set of conditions would return success instead of failure. This update fixes the get query dn failure. (BZ#572603) - If a master map entry is changed in any other way besides the map name (for example, map wide options) the system encountered two application data structures for the "same" map during a map re-read. If the contents of that map has also changed, a deadlock can occur.Having the duplicate data structure also caused entries in the problem map to be umounted. Since direct mount maps have a distinct autofs mount for each entry direct mount they appeared to stop working. This update corrects this behaviour. (BZ#514412)
- autofs would block for several minutes when attempting to mount from a server that was not available. A new mount_wait parameter has been added to prevent this block. This update requires SELinux policy 255 or later. (BZ#517349)
- The autofs parser objected to locations containing the characters '@' and '#' (Lustre and sshfs mounts) causing the mount request to fail. This update allows autofs to parse these characters and mount successfully. (BZ#520745)
- Due to an incorrect system call an error message stating "Operation not permitted" would be returned when attempting to mount an unknown hostname. This call has been corrected and autofs now returns "hostname lookup failed" as would be expected. (BZ#533323)
- A typing error in the usage text of the autofs service script has been corrected. (BZ#534012)
- When changing the timed wait from using select(2) to poll(2) in the non-blocking TCP connection function, to overcome the 1024 file handle limit of select(2), the wait timeout was not correctly converted from seconds to milliseconds. This update corrects the problem. (BZ#539747)
- autofs failed to mount locations whose path depended on another local auto-mounted mount. Dependent mounts are triggered by calling access(2) on the mount location path prior to mounting the location. The check for whether a location was a local path was restrictive and didn't cater for all cases. This has now been fixed. (BZ#537403)
- Inter-operability between autofs and some non-open source LDAP servers was impaired when a SASL authenticated connection was used over muliple bind and unbind operations. autofs has been updated use distinct authentication connection for each server it binds to. (BZ#537793)
- autofs failed to load its maps if all LDAP servers were down, or unreachable, when the daemon started. The dependency on an LDAP server being available at startup has been removed. This change resolved the issue of the map server being unreachable for some common usage cases. (BZ#543554)
- The random selection option used with mount locations that have multiple servers was not being set correctly during the paring of master map entries. If specified as a mount option in master map entries the option is now used as has been requested. (BZ#548476)
- Setting the expire timeout to 0 was causing autofs to constantly schedule expire runs leading to excessive resource usage and preature umounting of mounts. Setting the timeout to 0 should in fact disable expiry of mounts and this update fixes this incorrect behavior. (BZ#548277)
- autofs would abort when using DIGEST-MD5 authentication under heavy concurrent access. This was caused by autofs not providing the locking functions required by the cyrus-sasl library. In addition the cyrus-sasl library locking functions contained a race which sometimes lead to a deadlock. This update adds the needed locking functions to autofs and passes them to cyrus-sasl at initialization. The bug in the cyrus-sasl library is fixed in cyrus-sasl-lib 2.1.22-5.el5.el5_4.3 and later which is required for the update to install if cyrus-sasl is also installed. (BZ#559430)
1.9. automake
1.9.1. RHSA-2010:0321: Low security update
1.10. avahi
1.10.1. RHBA-2010:0034: bug fix update
Note
1.11. bind
1.11.1. RHSA-2010:0062: Moderate security update
Important
1.11.2. RHSA-2009:1620: Moderate security update
Important
1.12. binutils
1.12.1. RHBA-2010:0304: bug fix update
1.13. bogl
1.13.1. RHBA-2009:1593: bug fix update
Note
1.14. bootparamd
1.14.1. RHBA-2010:0057: bug fix update
Note
1.15. booty
1.15.1. RHBA-2010:0185: bug fix and enhancement update
1.16. brltty
1.16.1. RHSA-2010:0181: Low security and bug fix update
1.17. checkpolicy
1.17.1. RHBA-2010:0184: bug fix update
1.18. chkconfig
1.18.1. RHBA-2009:1628: bug fix update
Note
1.19. cman
1.19.1. RHBA-2009:1435: bug fix update
Note
1.19.2. RHBA-2009:1516: bug-fix update
Note
1.19.3. RHBA-2009:1598: bug fix update
Note
1.19.4. RHBA-2009:1622: bug-fix update
Note
1.19.5. RHBA-2010:0266: bug fix and enhancement update
1.20. cmirror
1.20.1. RHBA-2010:0307: bug fix update
1.21. cmirror-kmod
1.21.1. RHBA-2010:0309: bug fix update
1.22. conga
1.22.1. RHBA-2009:1623: bug fix update
Note
1.22.2. RHBA-2010:0289: bug fix and enhancement update
1.23. coolkey
1.23.1. RHBA-2010:0068: bug fix update
Note
1.24. coreutils
1.24.1. RHBA-2009:1511: bug fix update
Note
1.24.2. RHBA-2010:0120: bug fix update
Note
1.25. cpio
1.25.1. RHSA-2010:0144: Moderate security update
Important
1.26. cpuspeed
1.26.1. RHBA-2010:0035: bug fix update
Note
1.27. crash
1.27.1. RHBA-2010:0230: bug fix update
1.28. ctdb
1.28.1. RHEA-2010:0320: enhancement update
1.29. cups
1.29.1. RHBA-2010:0045: bug fix update
Note
1.29.2. RHSA-2010:0129: Moderate security update
Important
1.29.3. RHSA-2009:1595: Moderate security update
Important
1.29.4. RHSA-2009:1513: Moderate security update
Important
1.29.5. RHBA-2010:0210: bug fix update
1.30. curl
1.30.1. RHSA-2010:0273: Moderate security, bug fix and enhancement update
1.31. cyrus-imapd
1.31.1. RHSA-2009:1459: Important security update
Important
1.32. cyrus-sasl
1.32.1. RHBA-2010:0151: bug fix update
Note
1.33. dbus
1.33.1. RHSA-2010:0018: Moderate security update
Important
1.33.2. RHBA-2010:0236: bug fix update
1.34. dbus-python
1.34.1. RHBA-2009:1559: bug fix available
Note
1.35. device-mapper
1.35.1. RHBA-2010:0296: bug fix and enhancement update
1.36. device-mapper-multipath
1.36.1. RHBA-2009:1645: bug fix update
Note
1.36.2. RHBA-2010:0255: bug fix and enhancement update
1.37. dhcp
1.37.1. RHBA-2010:0042: bug fix update
Note
1.37.2. RHBA-2010:0223: bug fix update
1.38. dhcpv6
1.38.1. RHBA-2010:0196: bug fix update
1.39. dmidecode
1.39.1. RHEA-2009:1456: enhancement update
Note
1.39.2. RHEA-2010:0303: enhancement update
1.40. dmraid
1.40.1. RHBA-2010:0286: bug fix update
1.41. dogtail
1.41.1. RHBA-2010:0009: bug fix update
Note
1.42. dosfstools
1.42.1. RHBA-2010:0007: bug fix update
Note
1.43. dstat
1.43.1. RHSA-2009:1619: Moderate security update
Important
1.44. e4fsprogs
1.44.1. RHBA-2010:0239: bug fix and enhancement update
1.45. elilo
1.45.1. RHEA-2010:0302: enhancement update
1.46. elinks
1.46.1. RHSA-2009:1471: Important security update
Important
1.47. esc
1.47.1. RHBA-2010:0066: bug fix update
Note
1.48. etherboot
1.48.1. RHBA-2010:0227: bug fix update
1.49. ethtool
1.49.1. RHBA-2010:0279: bug fix and enhancement update
1.50. evince
1.50.1. RHBA-2010:0195: bug fix update
1.51. exim
1.51.1. RHBA-2009:1627: bug fix update
Note
1.52. fetchmail
1.52.1. RHSA-2009:1427: Moderate security update
Important
1.53. filesystem
1.53.1. RHBA-2009:1481: bug fix update
Note
1.54. firefox
1.54.1. RHSA-2010:0112: Critical security update
Important
1.54.2. RHSA-2009:1674: Critical security update
Important
1.54.3. RHSA-2009:1530: Critical security update
Important
1.54.4. RHSA-2009:1430: Critical security update
Important
1.55. firstboot
1.55.1. RHBA-2010:0314: bug fix update
1.56. freeradius
1.56.1. RHSA-2009:1451: Moderate security update
Important
1.56.2. RHBA-2009:1678: bug fix update
Note
1.57. gail
1.57.1. RHBA-2009:1594: bug fix update
Note
1.58. gcc
1.58.1. RHBA-2009:1533: bug fix update
Note
1.58.2. RHSA-2010:0039: Moderate and gcc4 security update
Important
1.58.3. RHBA-2010:0232: bug fix update
1.59. gd
1.59.1. RHSA-2010:0003: Moderate security update
Important
1.60. gdb
1.60.1. RHBA-2010:0285: bug fix update
1.61. gfs-kmod
1.61.1. RHSA-2010:0291: Moderate security, bug fix and enhancement update
1.62. gfs-utils
1.62.1. RHBA-2010:0290: bug fix update
1.63. gfs2-utils
1.63.1. RHBA-2010:0287: bug fix update
1.64. glibc
1.64.1. RHBA-2009:1634: bug fix update
Note
1.64.2. RHBA-2010:0050: bug fix update
Note
1.64.3. RHBA-2010:0306: bug fix and enhancement update
1.65. gnome-vfs2
1.65.1. RHBA-2010:0317: bug fix update
1.65.2. RHBA-2010:0032: bug fix update
Note
1.66. gpart
1.66.1. RHBA-2009:1606: bug fix update
Note
1.67. gzip
1.67.1. RHSA-2010:0061: Moderate security update
Important
1.68. hal
1.68.1. RHBA-2010:0256: bug fix update
1.69. hmaccalc
1.69.1. RHBA-2010:0055: bug fix update
Note
1.70. httpd
1.70.1. RHSA-2010:0168: Moderate security and enhancement update
Important
1.70.2. RHSA-2009:1579: Moderate security update
Important
1.70.3. RHBA-2010:0252: bug fix and enhancement update
1.71. hwdata
1.71.1. RHEA-2010:0197: enhancement update
1.72. ia32el
1.72.1. RHBA-2010:0250: bug fix update
1.73. iasl
1.73.1. RHBA-2010:0226: bug fix and enhancement update
1.74. inn
1.74.1. RHBA-2009:1509: bug fix update
Note
1.75. iproute
1.75.1. RHBA-2009:1520: bug fix update
Note
1.76. iprutils
1.76.1. RHEA-2010:0229: enhancement update
1.77. iptables
1.77.1. RHBA-2009:1539: bug fix update
Note
1.78. iptstate
1.78.1. RHBA-2009:1676: bug fix update
Note
1.79. ipw2200-firmware
1.79.1. RHEA-2010:0218: enhancement update
1.80. iscsi-initiator-utils
1.80.1. RHBA-2010:0078: bug fix update
Note
1.80.2. RHBA-2010:0293: bug fix and enhancement update
1.81. iwl3945-firmware
1.81.1. RHEA-2010:0219: enhancement update
1.82. iwl4965-firmware
1.82.1. RHEA-2010:0215: enhancement update
1.83. iwl5000-firmware
1.83.1. RHEA-2010:0216: enhancement update
1.84. java-1.6.0-ibm
1.84.1. RHBA-2010:0327: bug fix update
1.85. java-1.6.0-openjdk
1.85.1. RHSA-2009:1584: Important security update
Important
1.86. java-1.6.0-sun
1.86.1. RHBA-2010:0072: bug fix update
Note
1.87. kdelibs
1.87.1. RHBA-2009:1464: bug fix update
Note
1.87.2. RHSA-2009:1601: Critical security update
Important
1.88. kernel
1.88.1. RHSA-2011:0004: Important: kernel security, bug fix, and enhancement update
Important
Security fixes:
- A flaw was found in sctp_packet_config() in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation. A remote attacker could use this flaw to cause a denial of service. (CVE-2010-3432, Important)
- A missing integer overflow check was found in snd_ctl_new() in the Linux kernel's sound subsystem. A local, unprivileged user on a 32-bit system could use this flaw to cause a denial of service or escalate their privileges. (CVE-2010-3442, Important)
- A heap overflow flaw in the Linux kernel's Transparent Inter-Process Communication protocol (TIPC) implementation could allow a local, unprivileged user to escalate their privileges. (CVE-2010-3859, Important)
- An integer overflow flaw was found in the Linux kernel's Reliable Datagram Sockets (RDS) protocol implementation. A local, unprivileged user could use this flaw to cause a denial of service or escalate their privileges. (CVE-2010-3865, Important)
- A flaw was found in the Xenbus code for the unified block-device I/O interface back end. A privileged guest user could use this flaw to cause a denial of service on the host system running the Xen hypervisor. (CVE-2010-3699, Moderate)
- Missing sanity checks were found in setup_arg_pages() in the Linux kernel. When making the size of the argument and environment area on the stack very large, it could trigger a BUG_ON(), resulting in a local denial of service. (CVE-2010-3858, Moderate)
- A flaw was found in inet_csk_diag_dump() in the Linux kernel's module for monitoring the sockets of INET transport protocols. By sending a netlink message with certain bytecode, a local, unprivileged user could cause a denial of service. (CVE-2010-3880, Moderate)
- Missing sanity checks were found in gdth_ioctl_alloc() in the gdth driver in the Linux kernel. A local user with access to "/dev/gdth" on a 64-bit system could use this flaw to cause a denial of service or escalate their privileges. (CVE-2010-4157, Moderate)
- The fix for Red Hat Bugzilla bug 484590 as provided in RHSA-2009:1243 introduced a regression. A local, unprivileged user could use this flaw to cause a denial of service. (CVE-2010-4161, Moderate)
- A NULL pointer dereference flaw was found in the Bluetooth HCI UART driver in the Linux kernel. A local, unprivileged user could use this flaw to cause a denial of service. (CVE-2010-4242, Moderate)
- It was found that a malicious guest running on the Xen hypervisor could place invalid data in the memory that the guest shared with the blkback and blktap back-end drivers, resulting in a denial of service on the host system. (CVE-2010-4247, Moderate)
- A flaw was found in the Linux kernel's CPU time clocks implementation for the POSIX clock interface. A local, unprivileged user could use this flaw to cause a denial of service. (CVE-2010-4248, Moderate)
- Missing initialization flaws in the Linux kernel could lead to information leaks. (CVE-2010-3876, CVE-2010-4083, Low)
- BZ#651811
- Kernel panic could occur when the
gfs2_glock_hold
function was called within thegfs2_process_unlinked_inode
function. This was due to the fact thatgfs2_glock_hold
was being called without a reference already held on the inode in question. This update, resolves this problem by changing the order in which it acquires references to match that of the NFS code, thus, kernel panic no longer occurs. - BZ#651805
- Running certain tests (exploiting the reclaiming of unlinked dinodes) could cause a livelock to occur which resulted in a
GFS2
hang. This update fixes the problems with inodes getting stuck in certain states, thus, the hangs no longer occur. - BZ#646765
- The HP ProLiant DL580 G5 Server is in the
bfsort
whitelist, however the HP ProLiant DL580 G7 Server was not. This caused the scripts running under HP ProLiant DL580 G7 Server to not work properly. With this update, the HP ProLiant DL580 G7 Server has been added to thebfsort
whitelist. - BZ#652561
- When removing a slave
tg3
driver interface withvlan
support frombond
, a "scheduling while atomic" error (i.e. a thread has called theschedule()
function during an operation which is supposed to be atomic, i.e uninterrupted) occurred and, consequently, the system encountered a deadlock. With this update, the aforementioned error no longer occurs and removing a slavetg3
driver interface works as expected. - BZ#651818
- Loading a kernel module invokes various
kstopmachine
threads which repeat acquiring and releasing of each spinlock of their localrun queue
by calling theyield()
function. If an interruption occurs at that time and its handler requires one of those spinlocks, the operation fails to acquire the lock and the system hangs up. With this update,run queue
spinlock starvation is avoided, thus, the system no longer hangs. - BZ#643339
- If an Intel 82598 10 Gigabit Ethernet Controller was configured in a way that caused peer-to-peer traffic to be sent to the Intel X58 I/O hub (IOH), a PCIe credit starvation problem occurred. As a result, the system would hang. With this update, the system continues to work and does not hang.
- BZ#657028
- Handling ALUA (Asymmetric Logical Unit Access)
transitioning
states did not work properly due to a faultySCSI
(Small Computer System Interface)ALUA
handler. With this update, optimized state transitioning prevents the aforementioned behavior. - BZ#657029
- Due to a null pointer dereference in the
qla24xx_queuecommand
function, a Red Hat Enterprise Linux 5.5.z QLogic Fibre Channel host would panic during I/O with controller faults. This update fixes the null pointer dereference, thus, the system no longer panics. - BZ#658934
- Prior to this update, Red Hat Enterprise Linux 5 with the
qla4xxx
driver andFC
(Fibre Channel) drivers using thefc
class, a device might have been put in the offline state due to a transport problem. Once the transport problem was resolved, the device was not usable until a user manually corrected the state. This update enables the transition from the offline state to the running state, thus, fixing the problem. - BZ#657319
- System could have crashed when the
uhci_irq()
function was called between theuhci_stop()
andfree_irq()
functions. This update avoids the aforementioned crash and the system works as expected. - BZ#649255
- On some
bnx2
-based devices, frames could drop unexpectedly. This was shown by the increasingrx_fw_discards
values in theethtool --statistics
output. With this update, frames are no longer dropped and allbnx2
-based devices work as expected. - BZ#647681
- Prior to this update,
balance-rr
bonding did not work properly. This resulted in non-functioning network interfaces unless the thebond0
interface had thepromiscuous
mode enabled. With this update, networkbalance-rr
bonding works as expected, thus, preventing the aforementioned issue. - BZ#658857
- Prior to this update, the global
dentry
unused counter (nr_unused
) failed to update properly. As a result, the counter would contain negative values. When trying to reference the counter,dcache
would loop indefinitely. With this update, thenr_unused
counter has been updated, thus, it now works properly and no longer causes indefinite loops. - BZ#653335
- Previously, both
GFS
andGFS2
file systems performed poorly when compared to, for example, theext3
file system. With this update, steps have been taken to ensure the best performance possible with the aforementioned file systems. - BZ#643344
- Prior to this update, the execve utility exhibited the following flaw. When an argument and any environment data were copied from an old task's user stack to the user stack of a newly-execve'd task, the kernel would not allow the process to be interrupted or rescheduled. Therefore, when the argument or environment string data was (abnormally) large, there was no "interactivity" with the process while the
execve()
function was transferring the data. With this update, fatal signals (like CTRL-c) can now be received and handled and a process is allowed to yield to higher priority processes during the data transfer. - BZ#643347
- A typographical error in the
create_by_name()
function tested an error pointer (ERR_PTR
) againstdentry
instead of*dentry
. If "*dentry" was anERR_PTR
, it would be dereferenced in either themkdir()
function or thecreate()
function which could cause kernel panic. With this update, the typographical error has been fixed, thus, kernel panic no longer occurs in the aforementioned case. - BZ#658378
- Updated partner qualification injecting target faults uncovered a flaw where the Emulex
lpfc
driver would incorrectly panic due to a nullpnode
dereference. This update addresses the issue and was tested successfully under the same test conditions without the panic occurring. - BZ#658864, BZ#658379
- Updated partner qualification injecting controller faults uncovered a flaw where the Emulex
lpfc
driver panicked during error handling. With this update, kernel panic no longer occurs. - BZ#658079
- Updated partner qualification injecting controller faults uncovered a flaw where Fibre Channel ports would go offline while testing with Emulex LPFC controllers due to a faulty LPFC heartbeat functionality. This update changes the default behavior of the LPFC heartbeat to
off
. - BZ#643345
- Prior to this update, the
netback
driver failed to transition from theInitWait
state to theConnected
state after it was closed once. This was due to the fact that at the moment thenetdev_state_change
function was called, the interface was still down, so theNETDEV_CHANGE
event was not called. This update makes sure the interface is up (via theNETDEV_UP
event) and correctly changes the states. - BZ#648938
- AMD64 hosts on Intel Xeon processor 7500 series machines panicked when installing a Red Hat Enterprise Linux 4.8 KVM guest. This was due to a faulty value being generated in the
gso_size
variable that did not conform to the specification. With this update, faulty values are no longer generated and kernel panic no longer occurs. - BZ#664416
- Reading an empty file on an optional mount
sync/noac
of NFSv4 could cause kernel panic. This problem did not occur when an optional mount was set as a default. The kernel panic was caused by improperly setting thelock_context
field innfs_writepage_sync
. With this update, the aforementioned issue has been fixed and kernel panic no longer occurs. - BZ#663353
- Running certain tests, the system could crash due to an error in
nfs_flush_incompatible
. This was caused by problematic calls to thenfs_clear_context
function. With this update, calls to thenfs_clear_context
function work as expected and the system no longer crashes. - BZ#663381
- Writing to a file on optional mount
sync/noac
of NFSv4 could cause kernel panic. This problem did not occur when an optional mount was set as a default. The kernel panic was caused by thelock_context
field being added to thenfs_writedata
but missing the functionality to be filled out in thenfs_writepage_sync
codepath. With this update, a new function was added to properly handle thelock_context
field, thus, kernel panic no longer occurs.
- BZ#658520
- The
sfc
driver adds support for the Solarstorm SFC9000 family of Ethernet controllers.
1.88.2. RHSA-2010:0839: Moderate: kernel security and bug fix update
Important
NULL
pointer dereference flaw was found in the io_submit_one()
function in the Linux kernel asynchronous I/O implementation. A local, unprivileged user could use this flaw to cause a denial of service. (CVE-2010-3066, Moderate)
xfs_ioc_fsgetxattr()
function in the Linux kernel XFS file system implementation. A data structure in xfs_ioc_fsgetxattr()
was not initialized properly before being copied to user-space. A local, unprivileged user could use this flaw to cause an information leak. (CVE-2010-3078, Moderate)
__futex_atomic_op1
, __futex_atomic_op2
, and futex_atomic_cmpxchg_inatomic()
macros replaced the LOCK
prefix with a NOP
instruction. A local, unprivileged user could use this flaw to cause a denial of service. (CVE-2010-3086, Moderate)
tcf_act_police_dump()
function in the Linux kernel network traffic policing implementation. A data structure in tcf_act_police_dump()
was not initialized properly before being copied to user-space. A local, unprivileged user could use this flaw to cause an information leak. (CVE-2010-3477, Moderate)
sys_io_submit()
function in the Linux kernel asynchronous I/O implementation. A local, unprivileged user could use this flaw to cause an information leak. (CVE-2010-3067, Low)
802.3ad
link aggregation did not work properly when using the ixgbe
driver. This was caused due to an inability to form 802.3ad
-based bonds. With this update, the issue causing 802.3ad
link aggregation to not work properly has been fixed. (BZ#644822)
IGMP
join packets. With this update, the driver sends IGMP
join packets and the multicast domain is rejoined immediately. (BZ#640973)
UP
and PV
drivers, may have caused the guest to stop responding. With this update, HVM guest migration works as expected. (BZ#630989)
lvextend
during an intensive Virtual Guest power up caused this operation to fail. Since lvextend
was blocked, all components became non-responsive: vgs
and lvs
commands froze the session, Virtual Guests became Paused
or Not Responding
. This was caused by a faulty use of a lock. With this update, performing an lvextend
operation works as expected. (BZ#632255)
iomem
resources, which were enumerated using the PNP Motherboard resource descriptions, were not recognized and taken into consideration when gathering resource information. This could have caused MMIO-based requests to receive allocations that were not valid. With this update, system board iomem
resources are correctly recognized when gathering resource information. (BZ#629861)
NOT_READY
on standby path. (BZ#634977)
megaraid_sas
driver (for SAS based RAID controllers) handled physical disks and management IOCTLs (Input/Output Control). All physical disks were exported to the disk layer, allowing an oops in megasas_complete_cmd_dpc()
when completing the IOCTL command if a timeout occurred. One possible trigger for this bug was running mkfs
. This update resolves this issue by updating the megaraid_sas
driver to version 4.31. (BZ#619365)
RELEASE_LOCKOWNER
operation has been implemented for NFSv4 in order to avoid an exhaustion of NFS server state IDs, which could result in an NFS4ERR_RESOURCE
error. Furthermore, if the NFS4ERR_RESOURCE
error is returned by the NFS server, it is now handled correctly, thus preventing a possible reason for the following error:
NFS: v4 server returned a bad sequence-id error!
pmt_update_time()
function. With this update, time is kept accurately and no longer drifts backwards. (BZ#641915)
dasd_sleep_on
functions use a global wait queue when waiting for a CQR (Channel Queue Request). Previously, the wait condition checked the status
and devlist
fields of the CQR to determine if it is safe to continue. This evaluation may have returned true, although the tasklet did not finish processing the CQR and the callback function had not been called yet. When the callback was finally called, the data in the CQR could have already been invalid. With this update, the sleep_on
wait condition has a safe way to determine if the tasklet has finished processing, thus, preventing the aforementioned behavior. (BZ#638579)
ICMP
packets corrupted the kernel memory. This was caused by a flaw in net/ipv4/proc.c
. With this update, kernel memory is no longer corrupted when receiving 8 or more different types of ICMP
packets. (BZ#634976)
/proc/acpi/ibm/video
in order to prevent the aforementioned crash. (BZ#629241)
NULL
pointer in the lpfc_nlp_put()
function may have caused the system to crash. With this update, several changes have been made to ensure the correct reference count, resolving this issue. (BZ#637727)
dd
command on an iSCSI device with the qla3xxx driver may have caused the system to crash. This error has been fixed, and running the dd
command on such device no longer crashes the system. (BZ#637206)
divider=x
kernel parameter set to a value greater than 1 and that showed the following line of text in the kernel boot messages were the subject of the aforementioned behavior:
time.c: Using 3.579545 MHz WALL PM GTOD PM timer
log_mtts_per_seg
was increased from 5 to 7, increasing the amount of memory that can be registered. Machines with larger memory are now able to register more memory. (BZ#643806)
1.88.3. RHSA-2010:0504: Important: kernel security and bug fix update
Important
1.88.4. RHSA-2010:0046: Important security and bug fix update
Important
1.88.5. RHSA-2010:0147: Important security and bug fix update
Important
1.88.6. RHSA-2010:0019: Important security update
Important
1.88.7. RHSA-2009:1670: Important security and bug fix update
Important
1.88.8. RHSA-2009:1548: Important security and bug fix update
Important
1.88.9. RHSA-2009:1455: Moderate security and bug fix update
Important
1.88.10. RHSA-2010:0178: Important Red Hat Enterprise Linux 5.5 kernel security and bug fix update
1.88.10.1. Bug Fixes
1.88.10.1.1. Generic Kernel Features
- Add IRONLAKE support to AGP/DRM drivers. BZ#547908
- PCI AER: HEST FIRMWARE FIRST support. BZ#547762
- Extend tracepoint support. BZ#534178
- Update ibmvscsi driver with upstream multipath enhancements. BZ#512203This update provides improved support for the ibmvscsi driver, including support for fastfail mode and improved multipathing support.This update is
64-bit PowerPC
-specific. - amd64_edac: Add and detect ddr3 support. BZ#479070
- Add scsi and libfc symbols to whitelist_file. BZ#533489
- Extend KABI to support symbols that are not part of the current KABI. BZ#526342
libfc
bug fixes and improvements. BZ#526259- Implement
smp_call_function_[single|many]
in x86_64 and i386. BZ#526043A number of updates now depend on thesmp_call_function_single()
andsmp_call_function_many()
functions. This update provides a single function that can refer to the appropriate function as required, thereby simplifying the creation of further updates. - Support the single-port Async device on p7 Saturn. BZ#525812
- Backport open source driver for Creative X-Fi audio card. BZ#523786
- [Intel 5.5 FEAT] Update PCI.IDS for B43 graphics controller. BZ#523637
- Support physical CPU hotplug. BZ#516999This feature provides the functionality to add and remove CPU resources physically while the system is running.This feature applies to 32-bit x86, 64-bit Intel 64 and AMD64, and 64-bit Itanium2 architectures.
- Include core WMI support and Dell-WMI driver. BZ#516623
- [kabi] Add scsi_nl_{send_vendor_msg,{add,remove}_driver}. BZ#515812
- Enable ACPI 4.0 power metering. BZ#514923
- Add AER software error injection support. BZ#514442
- Add support for Syleus chip to fschmd driver. BZ#513101
- Implement support for DS8000 volumes. BZ#511972
- Support Lexar ExpressCard. BZ#511374
- Disable ARB_DISABLE on platforms where it is not needed. BZ#509422ARB_DISABLE is a NOP on all of the recent Intel platforms. For such platforms, this update reduces contention on the c3_lock by skipping the fake ARB_DISABLE.This lock is held on each deep C-state entry and exit and with 16, 32, and 64 logical CPUs in NHM EP, NHM EX platforms, this contention can become significant. Specifically on distributions that do not have tickless feature and where all CPUs may wake up around the same time.
- Add
zfcp
parameter to dynamically adjust scsi_queue_depth size. BZ#508355 - Add HP ipmi message handling to Red Hat Enterprise Linux 5. BZ#507402
- Backport CONFIG_DETECT_HUNG_TASK to Red Hat Enterprise Linux 5. BZ#506059In some circumstances, tasks in the kernel may permanently enter the uninterruptible sleep state (D-State), making the system impossible to shut down. This update adds the Detect Hung Task kernel thread, providing the ability to detect tasks permanently stuck in the D-State.This new feature is controlled by the "CONFIG_DETECT_HUNG_TASK=" kernel flag. When set to "y", tasks stuck in the D-State are detected; when set to "n" it is off. The default value for the "CONFIG_DETECT_HUNG_TASK" flag is "y".Additionally, the "CONFIG_BOOTPARAM_HUNG_TASK_PANIC" flag has been added. When set to "y", a kernel panic is triggered when a task stuck in the D-State is detected. The default value for the "CONFIG_BOOTPARAM_HUNG_TASK_PANIC" flag is "n".
- Add ability to access Nehalem uncore configuration space. BZ#504330Systems that don't use MMCONFIG have trouble when allocating resources by using a legacy PCI probe. As a result, the machine will hang during boot if the Disk PCI device is not properly initialized.This update reverts a patch that improves the PCI ID detection in order to detect the new PCI devices found on Nehalem machines. Consequently, the kernel will not hang on such machines. A different patch will be needed, however, when adding any driver that needs to see the non-core set of PCI devices on Nehalem.
- When booted with P-state limit, limit can never be increased BZ#489566
- Add do_settimeofday and __user_walk_fd BZ#486205
- A bug was discovered where closing the lid on an HP6510b caused the system to crash. This was due to the system failing to run on CPU0. A patch was created to enable ACPI workqueues to run on CPU0, and this has been tested successfully. BZ#485016
- Some applications (e.g., dump and nfsd) try to improve disk I/O performance by distributing I/O requests to multiple processes or threads by using the Completely Fair Queuing (CFQ) I/O scheduler. This application design negatively affected I/O performance, causing a large drop in performance under certain workloads on real queuing devices.
- Enable CONFIG_DETECT_HUNG_TASK by default, but disable BOOTPARAM_xx by default
- Only prompt for network configuration when required. BZ#506898Due to an unexpected side effect of a kernel change in Red Hat Enterprise Linux 5.4, the installer will prompt for the network configuration, regardless of whether these parameters appear in the PARM or CONF files.This flaw was addressed by removing the annotation of cmdline as __initdata. The installer no longer prompts for network configuration when not required.
1.88.10.1.2. Kernel Platform Enablement
1.88.10.1.2.1. BX-EX/MC Enablement Features
- [Intel 5.5 FEAT] Make suspend-resume work on systems with lots of logical CPUs (Boxboro-EX). BZ#499271
- [Intel 5.5 FEAT] Add ability to access Nehalem uncore config space 504330/539675
- [AMD 5.5 Feat] Support Magny-cours topology 513684/539678
- Red Hat Enterprise Linux 5.5: Power-aware Scheduler changes to support multiple node processors 513685/539680
- Fix kernel panic while booting Red Hat Enterprise Linux 5 32-bit kernel on Magny-cours. BZ#522215
- [Intel 5.5 FEAT] Oprofile: Add support for arch perfmon - kernel component BZ#523479
- EXPERIMENTAL EX/MC: Xen NUMA broken on Magny-cours system Z. BZ#526051
- [Intel 5.5 FEAT] Fix spinlock issue which causes performance impact on large systems. BZ#526078
- EXPERIMENTAL EX/MC: Magny-cours topology fixes. BZ#526315
- EXPERIMENTAL MC/EX: Issue when bringing CPU offline and online with 32-bit kernel. BZ#526770
- EXPERIMENTAL MC/EX: Incorrect memory setup can cause Xen crash. BZ#526785
- Fix AMD erratum - server C1E BZ#519422
- EXPERIMENTAL EX/MC: AMD IOMMU Linux driver with latest BIOS has IO PAGE FAULTS 531469/539689
- [Intel 5.5 BUG] NMI and Watchdog are not disabled on CPU when CPU is taken offline. BZ#532514
- Boxboro-EX: multiple equal directory entries in
/proc/acpi/processor
BZ#537395
1.88.10.1.2.2. x86-specific Updates
- Fix AMD Magny-Cours boot inside Xen on pre-5.5 hypervisor. BZ#560013A problem was found where Beta 1 of Red Hat Enterprise Linux 5.5 would fail to boot as a Xen guest on AMD Magny-Cours systems using a hypervisor other than the one included in Red Hat Enterprise Linux 5.5.This update provides a fix for this issue.
- Support always running local APIC. BZ#496306
- kvm: Mark kvmclock_init as cpuinit. BZ#523450
- Fix stale data in shared_cpu_map cpumasks. BZ#541953This update was necessary to avoid possible kernel panic when performing frequent CPU online/offline operations.
1.88.10.1.2.3. x86_64-specific Updates
- k8: Do not mark early_is_k8_nb as __init. BZ#567275This update addresses a problem with CPU hotplugging identified on AMD Magny-Cours machines.
- Avoid deadlocks during MCE broadcasts. BZ#562866
- Wire up compat sched_rr_get_interval. BZ#557092A problem was found where if a program that calls
sched_rr_get_interval()
is compiled on x86 and is executed on x86_64, it will destroy the user stack. This problem is solved by callingsys32_sched_rr_get_interval()
instead ofsys_sched_rr_get_interval()
whensched_rr_get_interval()
is called.This update includes a backport of an upstream patch to correct this problem. - Disable vsyscall in kvm guests. BZ#542612A problem was found on Red Hat Enterprise Linux 5.4 guests with PV clock enabled, where there is a large difference between the time returned by
clock_gettime(CLOCK_REALTIME)
and the time returned bygettimeofday()
, even if a program executes one call right after the other.This update addresses the problem, which was traced to the use of vsyscall in kvm guests. - Resolve issue with SCTP messages arriving out of order. BZ#517504A problem was found where, under the right conditions, it was possible for packets to become re-ordered prior to the assignment of a Transmission Sequence Number (TSN) value. The conditions which caused this are the fact that multiple interfaces were used in transmission, where each had differing Path Maximum Transmission Unit (pmtu) values.This update addresses the problem with the SCTP stack that allowed this reordering to occur.
- Cap kernel at 1024G on x86_64 systems.
- Fix kernel crash when 1TB of memory and NUMA is used. BZ#523522
- kvm: Allow kvmclock to be overwritten. BZ#523447
- glibc should call pselect() and ppoll() on Itanium kernels. BZ#520867
- Force Altix drivers to use 64-bit addressing. This update is Altix-specific. BZ#517192This update applies to the 64-bit Itanium2 architecture.
- vsmp: Fix bit-wise operator and compile issue. BZ#515408
- Fix hugepage memory tracking. BZ#518671
1.88.10.1.2.4. IBM S/390-specific Updates
- qeth: Set default BLKT settings by OSA hw level. BZ#559621A problem was found where new hardware was being configured with values for old hw levels, because BLKT settings were not being set according to different hw levels.This update ensures that the BLKT settings are applied after the hw level has been probed.
- Clear high-order bits after switching to 64-bit mode. BZ#546302
- Fix single stepping on svc 0. BZ#540527A problem was found where if a system call number > 256 is single-stepped or svc 0 is single-stepped then the system call would not be executed. This update provides a solution to this problem.
- DASD: Support DIAG access for read-only devices. BZ#537859
- IUCV: Use correct output register in
iucv_query_maxconn()
. BZ#524251A problem was found where the system log contained kernel messages reporting that the IUCV "pathid" was greater thanmax_connections
. This is because the wrong output register was used when querying the maximum number of IUCV connections.This update ensures that the correct output register is used, and this problem no longer occurs. - cio: Fix set online/offline processing failures. BZ#523323A problem was found where the
set online
orset offline
routines failed for a DASD device. Afterwards this device could neither be set online nor offline.Theset online
,set offline
, and related rollback and error routines are only processed if the device is in a FINAL or DISCONNECTED state. - DASD: Fail requests when device state is less then ready. BZ#523219A problem was found where in certain device mapper multipath/PPRC setups a DASD device gets quiesced and then set to the "basic" state to flush its queue and return all already queued requests back to the device mapper. It was possible that a request was queued after the device's state was set to basic, and so that request stayed queued, was not processed, and the device mapper was blocked waiting for it.This update ensures that all requests that arrive in such a state are returned as failed.
- Set preferred IBM S/390 console based on conmode. BZ#520461A problem was found where if conmode was set to 3270 to enable the 3270 terminal device driver, kernel console messages were not displayed in the console view. This is because the default preferred console is set to "ttyS". For the 3270 terminal device driver, the preferred console must be set to "tty3270".This update introduces a new function to set the preferred console based on the specified conmode.
- Optimize storage key operations for anonymous pages. BZ#519977A problem was found where removal of anonymous mappings resulted in poor performance. This update optimizes the instructions that are used for these operations.
- CIO: set correct number of internal I/O retries. BZ#519814A problem was found where if a device has
n
paths and that device is not path-grouped, and an internal I/O command fails, then the control unit presents the error sensen
times on each different path. Because CIO only performs five retries, devices with five or more paths run out of retries before their functional status can be correctly determined.This update increases the number of retries to 10 to prevent this problem from occurring. - Add module signing to IBM S/390 kernels. BZ#483665
- Make CIO_* macros safe if dbfs are not available. BZ#508934
- qeth: Improve no_checksumming handling for layer3. BZ#503238
- qeth: Handle VSwitch Port Isolation error codes. BZ#503232
- Implement AF_IUCV SOCK_SEQPACKET support. BZ#512006This update offers AF_IUCV datagram stream-oriented sockets in addition to the existing AF_IUCV byte stream-oriented sockets. SOCK_SEQPACKET provides a sequenced, reliable, two-way connection-based data transmission path for datagrams of fixed maximum length; a consumer is required to read an entire packet with each input system call.
- Kernel parameters vmhalt, vmpanic, vmpoff and vmreboot are ignored. BZ#518229A problem was found where an obsolete function (
__setup()
) was being called twice. This update removes those function calls, and the affected kernel parameters now behave as expected.
1.88.10.1.2.5. Other Updates
- [PowerPC] Fix "scheduling while atomic" error in alignment handler. BZ#543637
- [powerpc] Handle SLB resize during migration. BZ#524112
- Export additional CPU flags in
/proc/cpuinfo
BZ#517928Previously,/proc/cpuinfo
only showed the original set of flags supported from the base kernel release. It did not include new features present in supported CPUs. This update addresses this problem, and applies to both x86 and x86_64 architectures. - This feature provides the ability for user level software monitoring the system for disabled cache indices and to explicitly disable them. BZ#517586This update applies to 32-bit x86 and 64-bit Intel 64 and AMD64 architectures.
- Update ALSA HDA, snd-hda-intel driver. BZ#525390
- Add Hudson-2 sb900 i2c driver. BZ#515125
- Add fcocee npiv support to ibmvfc driver. BZ#512192
- Add i3200 edac driver support. BZ#469976
1.88.10.1.3. Virtualization Updates
- Fix module loading for virtio-balloon module. BZ#564361
- VT-d: Ignore unknown DMAR entries. BZ#563900
- kvm: Fix double registering of pvclock on i386. BZ#557095
- Fix frequency scaling on Intel platforms. BZ#553324
- Update to enable VF in Dom0. BZ#547980
- Xen IOMMU fix for AMD M-C platforms with SATA set to IDE combined mode. BZ#544021AMD M-C systems, that is, Maranello platforms, have several SATA settings, for example, IDE, SATA AHCI, and SATA IDE combined mode. A problem was found with IOMMU when the SATA drive is in IDE combined mode that could prevent Red Hat Enterprise Linux 5.4 from booting properly when IOMMU is enabled. In some cases the SATA drive was not detected.This update implements a global interrupt remapping table, which is shared by all devices and provides better compatibility with certain old BIOSes, and prevents this problem from occurring.
- Ensure a new xenfb thread is not created on every save/restore. BZ#541325A problem was found where an initial two xenfb threads were created for a save/restore operation for a live migration, followed by another two every time the guest was live migrated, or saved and restored.This update avoids creating further threads if one already exists.
- PV guest crash on poweroff. BZ#540811
- Call trace error when resuming from suspend to disk. BZ#539521
- Add BL2xx and DL7xx to the list of ProLiant systems in
xen/arch/x86/ioport_emulate.c
in the Xen variants of Red Hat Enterprise Linux 5. BZ#536677 - Mask out extended topology CPUID feature. BZ#533292On Intel Nehalem (55xx) dom0 hosts, booting Windows 2008 R2 64-bit domU resulted in a hang. This was caused by incomplete emulation of the CPUID instruction in hvm/xvm support.Because Xen guests do not need to know about extended topology, this update masks out that topology to prevent this problem from occurring.
- Fix timedrift on VM with pv_clock enabled. BZ#531268
- Use upstream
kvm_get_tsc_khz()
BZ#531025 - Whitespace updates in Xen scheduler. BZ#529271
- Xen panic in msi_msg_read_remap_rte with acpi=off. BZ#525467
- Backport interrupt rate limiting. BZ#524747
- RHEV: SAP SLCS 2.3 fails during install/import in a RHEV-H/KVM guest with PV KVM clock. BZ#524076
- Attempting to boot a fully virtualized DomU with rawhide's 2.6.31-14.fc12.x86_64 for installation hangs almost immediately. A 32-bit HVM booted and installed successfully on a 32-bit host.This update masks out the
xsave
andosxsave
bits to prevent this problem from occurring. - Enable display of the
ida
flag on Xen kernels. BZ#522846Theida
flag, which indicates the presence of the Turbo Boost feature, was not seen in the cpuflags section of/proc/cpuinfo
on Xen kernels. This occurred on both 32-bit and 64-bit Xen kernels.This update ensures that this flag is displayed when the Turbo Boost feature is present on Xen kernels. - Xen fails to boot on Itanium with > 128GB memory. BZ#521865A problem was found where attempting to boot a Xen kernel on Itanium systems with more than 128GB of RAM would result in a Xen panic. This problem was traced to a miscalculation of the Xen heap size.This update includes support for the
xenheap_megabytes
hypervisor option to address this problem. For example, if the installed memory exceeds 64GB, it is suggested to set the option to a value equal to the memory size in gigabytes. For example, on a system with 128GB of memory, theelilo.conf
file should include the directive:append="xenheap_megabytes=128 --"
- Fix SRAT check for discontiguous memory. BZ#519225A problem was found where Xen could ignore valid SRAT tables because it expects completely contiguous memory ranges, where the sum of the node memory is approximately equal to the address of the highest memory page. This is an incorrect assumption and prevents NUMA support from being enabled on some systems. This update addresses this assumption and prevents this problem from occurring.
- Allow booting with broken serial hardware. BZ#518338
- Fix for array out-of-bounds in blkfront. BZ#517238
- Enable Xen to build on gcc 4.4. BZ#510686
- Handle x87 opcodes in TLS segment fixup. BZ#510225
- Implement fully preemptible page table teardown. BZ#510037
- Fix timeout with PV guest and physical CDROM. BZ#506899
- Fix SR-IOV function dependency link problem. BZ#503837
- F-11 Xen 64-bit domU cannot be started with > 2047MB of memory. BZ#502826
- x86: Make NMI detection work. BZ#494120
- netback: call netdev_features_changed. BZ#493092
- Invalidate dom0 pages before starting guest. BZ#466681
- AMD IOMMU Xen pass-through support. BZ#531469
- Add balloon driver for KVM guests. BZ#522629
- Provide pass-through MSI-X mask bit acceleration V3. BZ#537734
- CD-ROM drive does not recognize new media. BZ#221676
- kvmclock: fix incorrect wallclock value. BZ#519771
- KMP for Xen kernel cannot be applied. BZ#521081A problem was found when creating KMP that includes the driver that uses the "pci_enable_msi/pci_disable_msi" function for the Xen kernel and applying it, error messages are printed out and KMP cannot be applied. This problem occurred on both i386 and x86_64 architectures.This update addresses this problem and these error messages no longer appear.
1.88.10.1.4. Network Device Drivers
- mlx4: pass attributes down to vlan interfaces BZ#573098
- r8169: fix assignments in backported net_device_ops BZ#568040
- virtio_net: refill rx buffer on out-of-memory BZ#554078
- be2net: critical bugfix from upstream BZ#567718
- tg3: fix 5717 and 57765 asic revs panic under load BZ#565964
- bnx2x: use single tx queue BZ#567979
- igb: fix WoL initialization when disabled in eeprom BZ#564102
- igb: fix warning in igb_ethtool.c BZ#561076
- s2io: restore ability to tx/rx vlan traffic BZ#562732
- ixgbe: stop unmapping DMA buffers too early BZ#568153
- e1000e: disable NFS filtering capabilites in ICH hw BZ#558809
- bnx2: update firmware and version to 2.0.8 BZ#561578
- mlx4: fix broken SRIOV code BZ#567730
- mlx4: pass eth attributes down to vlan interfaces BZ#557109
- ixgbe: initial support of ixgbe PF and VF drivers BZ#525577
- bnx2x: update to 1.52.1-6 firmware BZ#560556
- ixgbe: prevent speculatively processing descriptors BZ#566309
- tg3: fix 57765 LED BZ#566016
- tg3: fix race condition with 57765 devices BZ#565965
- forcedeth: fix putting system into S4 BZ#513203
- netfilter: allow changing queue length via netlink BZ#562945
- e1000e: fix deadlock unloading module on some ICH8 BZ#555818
- Wireless fixes from 2.6.32.2, 2.6.32.3, 2.6.32.4, & 2.6.32.7 BZ#559711
- be2net: latest bugfixes from upstream for Red Hat Enterprise Linux 5.5 BZ#561322
- cxgb3: add memory barriers BZ#561957
- igb: fix msix_other interrupt masking BZ#552348
- niu: fix deadlock when using bondin BZ#547943
- sky2: fix initial link state error BZ#559329
- iptables: fix routing of REJECT target packets BZ#548079
- niu: fix the driver to be functional with vlans BZ#538649
- igb: update driver to support End Point DCA BZ#513712
- tg3: update to version 3.106 for 57765 asic support BZ#545135
- bonding: fix alb mode locking regression BZ#533496
- e1000e: fix broken wol BZ#557974
- fixup problems with vlans and bonding BZ#526976
- ixgbe: upstream update to include 82599-KR support BZ#513707
- be2net: multiple bug fixes BZ#549460
- virtio_net: fix tx wakeup race condition BZ#524651
- Add support for send/receive tracepoints. BZ#475457
- wireless: fix build when using O=objdir BZ#546712
- update tg3 driver to version 3.100 BZ#515312
- e1000e: support for 82567V-3 and MTU fixes BZ#513706
- bonding: add debug module option BZ#546624
- ipv4: fix possible invalid memory access BZ#541213
- s2io: update driver to current upstream version BZ#513942
- wireless: report reasonable bitrate for 802.11n BZ#546281
- mac80211: report correct signal for non-dBm values BZ#545899
- wireless: Remove some unnecessary warning messages. mac80211: avoid uninit pointer dereference in ieee80211. BZ#545121
- wireless: avoid deadlock when enabling rfkill BZ#542593
- bnx2: update to version 2.0.2 BZ#517377
- cnic: Update driver for Red Hat Enterprise Linux 5.5 BZ#517378
- mdio: Add mdio module from upstream and ethtool. Add more defines for mdio to use. Add the sfc (Solarflare) driver. BZ#448856
- r8169: update to latest upstream for Red Hat Enterprise Linux 5.5 BZ#540582
- benet: update driver to latest upstream for Red Hat Enterprise Linux 5.5 BZ#515269
- e1000: update to latest upstream for Red Hat Enterprise Linux 5.5 BZ#515524
- ipv4: fix an unexpectedly freed skb in tcp BZ#546402
- bnx2: fix frags index BZ#546326
- netxen: further p3 updates for Red Hat Enterprise Linux 5.5 BZ#542746
- netxen: driver updates from 2.6.31 and 2.6.32 BZ#516833
- igb: update igb driver to support barton hills BZ#513710
- enic: update to upstream version 1.1.0.100 BZ#519086
- ipvs: synchronize closing of connections BZ#492942
- cxgb3: fix port index issue and correct hex/decimal error BZ#516948
- mlx4_en: add a pci id table BZ#508770
- resolve issues with vlan creation and filtering BZ#521345
- gro: fix illegal merging of trailer trash BZ#537876
- ixgbe: add and enable CONFIG_IXGBE_DCA BZ#514306
- call cond_resched in rt_run_flush BZ#517588
- igb: add support for 82576ns serdes adapter BZ#517063
- qlge: updates and fixes for Red Hat Enterprise Linux 5.5 BZ#519453
- igb: fix kexec with igb controller BZ#527424
- qlge: fix crash with kvm guest device passthrough BZ#507689
- igb: set vf rlpml must take vlan tag into account BZ#515602
- fix race in data receive/select BZ#509866
- augment raw_send_hdrinc to validate ihl in user hdr BZ#500924
- bonding: introduce primary_reselect option and ab_arp use std active slave select code BZ#471532
- use netlink notifications to track neighbour states and introduce generic function __neigh_notify BZ#516589
- sched: fix panic in bnx2_poll_work BZ#526481
- bnx2i/cnic: update driver version for Red Hat Enterprise Linux 5.5 BZ#516233
- cxgb3: bug fixes from latest upstream version BZ#510818
- sunrpc: remove flush_workqueue from xs_connect BZ#495059
- lvs: adjust sync protocol handling for ipvsadm -2 and for timeout values BZ#524129
- igb and e100: return PCI_ERS_RESULT_DISCONNECT on failure BZ#514250
- bnx2: apply BROKEN_STATS workaround to 5706/5708 BZ#527748
- syncookies: support for TCP options via timestamps and tcp: add IPv6 support to TCP SYN cookies BZ#509062
- e1000e: return PCI_ERS_RESULT_DISCONNECT on fail BZ#508387
- e100: add support for 82552 BZ#475610
- netfilter: honour source routing for LVS-NAT BZ#491010
- Update r8169 driver to avoid losing MSI interrupts. BZ#514589
- ipt_recent: sanity check hit count BZ#523982
- ipv4: ip_append_data handle NULL routing table BZ#520297
- fix drop monitor to not panic on null dev BZ#523279
- ipv6: do not fwd pkts with the unspecified saddr BZ#517899
- igbvf: recognize failure to set mac address BZ#512469
- sunrpc client: IF for binding to a local address and set rq_daddr in svc_rqst on socket recv BZ#500653
- tcp: do not use TSO/GSO when there is urgent data BZ#502572
- vxge: new driver for Neterion 10Gb Ethernet and Makefile, Kconfig and config additions BZ#453683
- 8139too: RTNL and flush_scheduled_work deadlock BZ#487346
- icmp: fix icmp_errors_use_inbound_ifaddr sysctl BZ#502822
- bonding: allow bond in mode balance-alb to work BZ#487763
- rtl8139: set mac address on running device BZ#502491
- tun: allow group ownership of TUN/TAP devices BZ#497955
- tcp: do not use TSO/GSO when there is urgent data BZ#497032
- A problem was found where if you set
/proc/sys/net/ipv4/route/secret_interval
to0
, you could not reset it to another value, and/bin/bash
would hang on the echo.The timer reschedule path was updated to ensure that the rtnl lock is always released. The/proc/sys/net/ipv4/route/secret_interval
can now be set to0
and successfully reset to another value without causing/bin/bash
to hang. BZ#510067 - sky2: revert some phy power refactoring changes BZ#509891
- bonding: tlb/alb: set active slave when enslaving BZ#499884
- tg3: refrain from touching MPS BZ#516123
- qlge: fix hangs and read performance BZ#517893
- mlx4_en fix for vlan traffic BZ#514141
- mlx4_en device multi-function patch BZ#500346
- mlx4_core: fails to load on large systems BZ#514147
- add DSCP netfilter target BZ481652#
1.88.10.1.5. Filesystem and Storage Management Updates
1.88.10.1.5.1. NFS-specific Updates
- Fix a deadlock in the sunrpc code. BZ#548846
- Ensure
dprintk()
macro works everywhere. BZ#532701 - Update
nfs4_do_open_expired()
to prevent infinite loops. BZ#526888A problem was found withnfs4_do_open_expired()
that could lead to the reclaimer thread going into an infinite loop. This bug was triggered when the client received an NFS4ERR_DELAY from the server, and the exception.retry bit was set, enforcing a timeout. This bit was never reset to zero (0) when the server recovered, leading to an infinite loop.This update checks for server recovery and resets the exception.retry bit when appropriate, preventing the creation of this infinite loop. - nfsnobody == 4294967294 causes idmapd to stop responding BZ#519184
- statfs on NFS partition always returns 0 BZ#519112A problem was found where
statfs
on NFS partitions always returned a zero (0) value, regardless of success or fail. On fail,statfs
should return a negative number.This update corrects the problem so thatstatfs
behaves as expected. - Read/Write NFS I/O performance was severely degraded by NFS synchronous write RPCs (FILE_SYNC) that occur when an application has a file open O_RDWR and is reading dirty pages. This read() system call triggered a flush of the dirty page to the server, using a 4096-byte synchronous write. The remote filesystem is mounted with an explicit async mount option, and the application does not open the file with O_SYNC or O_DSYNC flags.
- Mounting with a rsize/wsize of 2048 (less than the 4096 page size) eliminates these synchronous writes, and dramatically improves I/O. BZ#498433
- knfsd: query fs for v4 getattr of FATTR4_MAXNAME BZ#469689
- Bring nfs4acl into line with mainline code BZ#479870
- Add an nfsiod workqueue BZ#489931
- nfsv4: Distinguish expired from stale stateID BZ#514654
- Do an exact check of attribute specified BZ#512361In case ACLs are not supported in the underlying filesystem, this update enables the NFSv4 server to return NFS4ERR_ATTRNOTSUPP when ACL attributes are specified when creating a file.
- Fix regression in nfs_open_revalidate BZ#511278
- Fix cache invalidation problems in nfs_readdir BZ#511170
1.88.10.1.5.2. GFS-specific Updates
- Fix kernel BUG when using fiemap. BZ#569610
- Use correct GFP for allocating page on write. BZ#566221Allocation of memory during the write system call can trigger memory reclaim. This update ensures that the VM does not call back into the filesystem, resulting in a kernel OOPS. This problem is only seen in times of memory shortage on a node.
- Filesystem mounted with ecryptfs_xattr option could not be written. BZ#553670
- Filesystem consistency error in gfs2_ri_update. BZ#553447
- Update O_APPEND to behave as expected. BZ#544342Previously, when using GFS2, if two nodes concurrently updated the same file, each node would overwrite the other node's data, as the file position for such a file was not being updated correctly. This issue only occurred when using
open()
with the O_APPEND flag, and then issuing awrite()
without first performing another operation on the inode, such asstat()
orread()
. - Fix glock reference count issues. BZ#539240
- Fix rename locking issue. BZ#538484
- Enhance statfs and quota usability. BZ#529796
- Cluster failures due to invalid metadata blocks. BZ#519049A problem was found with gfs2 filesystems where clusters would fail as a result of fatal filesystem withdrawal. This update provides a solution to that problem.
- gfs2_delete_inode failing on RO filesystem. BZ#501359
- Fix potential race in glock code. BZ#498976
- GFS2 ">>" will not update ctime and mtime after appending to the file. BZ#496716
- After gfs2_grow, new size is not seen immediately. BZ#482756
- Add '-o errors=withdraw|panic' to GFS2 mount option. BZ#518106
- mount.gfs hangs forever if concurrent umount of different gfs filesystems are performed. BZ#440273
1.88.10.1.5.3. CIFS-specific Updates
- CIFS filesystem update, including: BZ#562947
- Fix length calculation for converted Unicode readdir names.
- Fix dentry hash calculation for case-insensitive mounts.
- Do not make mountpoints shrinkable.
- Ensure maximum username length check in session setup matches.
- NULL out pointers when chasing DFS referrals. BZ#544417
- Protect GlobalOplock_Q with its own spinlock to prevent crash in small_smb_init. BZ#531005
- Add new options to disable overriding of ownership. BZ#515252
- cifs: Enable dfs submounts to handle remote referrals. BZ#513410
httpd
Sendfile problems reading from a CIFS share. BZ#486092- Don't use
CIFSGetSrvInodeNumber
BZ#529431 - CIFS filesystem update, including: BZ#500838
- Fix artificial limit on reading symlinks
- Copy struct *after* setting port, not before
- Add addr= mount option alias for ip=
- Free nativeFileSystem before allocating new one
- Fix read buffer overflow
- Fix potential NULL deref in parse_DFS_referrals
- Fix memory leak in ntlmv2 hash calculation
- Fix broken mounts when an SSH tunnel is used
- Avoid invalid kfree in cifs_get_tcp_session
1.88.10.1.5.4. Cluster-specific Updates
- dlm: Fix connection close handling. BZ#521093A problem was found where a cluster would hang after a node rejoins from a simulated network outage. This update addresses the connection close handling problem that was the cause of the issue, and clusters now behave as expected in this situation.
1.88.10.1.5.5. Other Updates
- Fix randasys crashes x86_64 systems regression. BZ#562857
- proc: Make errno values consistent when race occurs. BZ#556545
- Fix performance regression introduced by eventfd support. BZ#548565OLTP-type runs regressed by 0.5% due to the additional overhead in the
aio_complete()
code path.This update uses a bit inki_flags
to address this problem. - Fix possible inode corruption on unlock. BZ#545612
- xfs: Fix fallocate error return sign. BZ#544349When issuing an fallocate call on xfs which results in insufficient space to complete, XFS returns "28" instead of "ENOSPC" - xfs uses positive errnos internally, and flips them before returning, but in this case it was missed.This update ensures the error number is inverted before being returned.
- Skip inodes without pages to free in
drop_pagecache_sb()
. BZ#528070 - Fix soft lockup problem with
dcache_lock
. BZ#526612 - ext3: Replace
lock_super
with explicit resize lock. BZ#525100A problem was found where performing an online resize of an ext3 filesystem would fail. This update cross-ports a change developed for ext4 to address a similar problem. - Update MPT fusion 3.4.13rh BZ#516710The mtp base driver for devices using LSI Fusion MPT firmware has been updated to version 3.4.13rh. This update fixes many issues, most notably:
- The serial attached SCSI (SAS) topology scan has been restructured, adding expander, link status and host bus adapter (HBA) events.
- Intermittent issues caused by SAS cable removal and reinsertion have been fixed.
- An issue where SATA devices received different SAS addresses has been fixed.
- The device firmware now reports the queue full event to the driver and the driver handles the queue full event using the SCSI mid-layer.
- Update MPT2SAS to 02.101.00.00 BZ#516702The mpt2sas driver that supports the SAS-2 family of adapters from LSI has been updated to version 02.101.00.00. This update fixes many issues, most notably:
- Sanity checks have been added when volumes are added and removed, ignoring events for foreign volumes.
- The driver is now legacy I/O port free.
- An issue that may have resulted in a kernel OOPS at hibernation or resume has been fixed.
- Fix online resize bug while using
resize2fs
BZ#515759 - ENOSPC during fsstress leads to filesystem corruption on ext2, ext3, and ext4 BZ#515529
- Bring putpubfh handling inline with upstream BZ#515405
- Address file write performance degradation on ext2 file systems BZ#513136When file write performance is measured using the iozone benchmark test, the performance of Red Hat Enterprise Linux 5.4 GA Snapshot1 is about 40% lower than the performance of Red Hat Enterprise Linux 5.3 GA in some cases. File read performance of 5.4 GA Snapshot1 is almost the same as 5.3 GA.This problem occured on both i386 and x86_64, however i386 performance degradation seemed to be worse compared to x86_64.This update converts ext2 to the new aops.
- getdents() reports
/proc/1/task/1/
as DT_UNKNOWN BZ#509713 - Do not return invalidated nlm_host BZ#507549
- Make NR_OPEN tunable BZ#507159
- Free journal buffers on ext3 and ext4 file systems after releasing private data belonging to a mounted filesystem BZ#506217
- Prevent Genesis from getting stuck in a loop writing to an unlinked file BZ#505331
- Fix inode_table test in ext{2,3}_check_descriptors BZ#504797
- Support origin size < chunk size BZ#502965
- smbd proccess hangs with flock call BZ#502531
- inotify: fix race BZ#499019
- Don't allow setting ctime over v4 BZ#497909
- AVC denied 0x100000 for a directory with eCryptFS and Apache BZ#489774
- Don't zero out pages array inside struct dio BZ#488161
- File truncations when both suid and write permissions are set BZ#486975
- Fix stripping SUID/SGID flags when chmod/chgrp directory BZ#485099
- Sanitize invalid partition table entries BZ#481658
- DIO write returns -EIO on try_to_release_page fail BZ#461100
- Batch AIO requests BZ#532769
- Add eventd support. BZ#493101
- Update ext4 to latest upstream codebase BZ#528054
- If a non-root setuid binary is run as root, its
/proc/<pid>/smaps
file cannot be read because the file's permissions only allow access from a task with the original root UID value.The/proc/<pid>/smaps
file is now created with S_IRUGO permissions (-r--r--r--), which means it can be read even when running a setuid binary. BZ#322881 - Correctly recognize the logical unit (LU) of Hitachi-made storage. BZ#430631The LU of Hitachi-made storage was not correctly recognized in Red Hat Enterprise Linux 5. The LU was correctly recognized using a combination of Red Hat Enterprise Linux 4, Hitachi-made storage, and the Qlogic-made HBA driver. Further, Red Hat Enterprise Linux 5 did recognize an LU that did not exist in the storage. The storage is used with SCSI-2.Red Hat Enterprise Linux 5 now issues a SCSI command (REPORT_LUN) when recognizing the logical unit in the SCSI layer. The LU is now correctly recognized when using a combination of Red Hat Enterprise Linux 5, Hitachi storage, and the Qlogic-made HBA driver.
1.88.10.1.6. Storage and Device Driver Updates
1.88.10.1.6.1. PCI Updates
- AER: Disable advanced error reporting by default. BZ#559978
- Prevent PCIe AER errors being reported multiple times. BZ#544923A problem was found where not all PCIe AER uncorrectable status bits were cleaned up after an uncorrectable/non-fatal or uncorrectable/fatal error was triggered. As a result, subsequent errors would sometimes display a previously reported error.This update ensures that errors are only reported once.
- Add base AER driver support. BZ#517093This feature provides the advanced error handling (diagnosis and recovery) for PCI-Express devices by adding AER (Advanced Error Reporting) support.PCIe AER provides the finer resolution of error source and error severity, as well as the ability to reset the slot to re-initialize the device.This update applies to 32-bit x86 and 64-bit Intel 64 and AMD64 architectures.
- Enable acs p2p upstream forwarding. BZ#518305
1.88.10.1.6.2. SCSI Updates
- mpt2sas: Fix missing initialization. BZ#565637
- be2iscsi: Fix scsi eh callouts and add support for new chip to be2iscsi driver. BZ#564145
- device_handler: Add netapp to ALUA device list. BZ#562080
- qla2xxx: Return FAILED if abort command fails. BZ#559972
- lpfc: Update driver to 8.2.0.63.3p FC/FCoE. BZ#564506
- lpfc: Update driver to 8.2.0.63.2p FC/FCoE. BZ#557792
- lpfc: Update driver to 8.2.0.63.1p FC/FCoE. BZ#555604
- be2iscsi: Upstream driver refresh for Red Hat Enterprise Linux 5.5. BZ#554545
- qla2xxx: Correct timeout value calculation for CT pass-through commands. BZ#552327
- qla2xxx driver updates. BZ#550148
- Update arcmsr driver to better match upstream. BZ#521203
- Re-enable "mpt_msi_enable" option. BZ#520820
- Kernel panics from list corruption when using a tape drive connected through cciss adapter. BZ#520192
- megaraid: Make driver legacy I/O port free. BZ#515863
- Update Emulex lpfc 8.2.0.x FC/FCoE driver. BZ#515272
- scsi_transport_fc: fc_user_scan correction to prevent scsi_scan looping forever. BZ#515176
- Update qla2xxx qla4xx driver. BZ#519447
- Update for HighPoint RocketRAID hptiop driver. BZ#519076
- Errata 28 fix on LSI53C1030. BZ#
- Add kernel (scsi_dh_rdace) support for Sun 6540 storage arrays. BZ#518496
- Disable state transition from OFFLINE to RUNNING. BZ#516934This feature prevents a timeout from occurring on the same device repeatedly by disabling the state transition of the SCSI device from OFFLINE to RUNNING in the
unblock
function of the SCSI layer.This update applies to 32-bit x86, 64-bit Intel 64 and AMD64, and 64-bit Itanium2 architectures. - Add be2iscsi driver. BZ#515284
- Add emc clarion support to scsi_dh modules. BZ#437107
- scsi_dh_rdac driver update. BZ#524335
- qla2xxx: Allow use of MSI when MSI-X disabled. BZ#517922On Red Hat Enterprise Linux 5 the MSI-X disable option for this driver also disables MSI. This update adds another state to the variable to allow the user to specify either MSI or MSI-X.
1.88.10.1.6.3. Other Updates
- Add Support for Huawei EC1260. BZ#517454
- Update stex driver to version 4.6.0102.4. BZ#516881
- Add support for the hp-ilo driver. BZ#515010
- Include support for SB900 SATA/IDE controllers. BZ#515114
- qla2xxx: add AER support. BZ#513927
- Add bfa Brocade BFA Fibre-Channel/FCoE driver. BZ#475695
- Add pmcraid driver. BZ#529979
- Update lpfc driver. BZ#549763
- Upddate megaraid driver. BZ#518243
1.88.10.1.7. Block Device Updates
- cfq-iosched: Fix sequential read performance regression. BZ#571818
- cfq: Kick busy queues without waiting for merged req. BZ#570814
- raid45: Fix for kernel OOPS resulting from constructor error path. BZ#565494
- Fix deadlock at suspending mirror device. BZ#555120
- Fix I/O errors while accessing loop devices or file-based Xen images from GFS volume. BZ#549397
- Correct issue with MD/DM mapping in blktrace. BZ#515551
- Fix install panic with xen iSCSI boot device. BZ#512991
- Allow more flexibility for read_ahead_kb store. BZ#510257
- Add device ID for 82801JI sata controller. BZ#506200
- Fix a race in dm-raid1. BZ#502927
- raid: deal with soft lockups during resync. BZ#501075
- blktrace stops working after a trace-file-directory replacement. BZ#498489
- I/O scheduler setting via elevator kernel option is not picked up by Xen guest. BZ#498461
- Fix rcu accesses in partition statistics code. BZ#493517
- Fix iosched batching fairness and reset batch for ordered requests. BZ#462472
1.88.10.1.8. Multiple Device Updates
- Fix kernel panic releasing bio structure after recovery failed. BZ#555171
- Lock snapshot while reporting status. BZ#543307A problem was found where, in the
snapshot_status()
function, the counts were being read without holding the lock. This could result in invalid intermediate values being reported.This update is a backport of a previous patch that locks the snapshot while reporting status. - Fix deadlock in device mapper multipath when removing a device. BZ#543270
- Snapshots of the same origin with differing chunk sizes causes corruption. BZ#210490The kernel driver dm-snapshot handles multiple snapshots with different chunk sizes incorrectly. It occasionally dispatches write requests to the origin volume prior to copying the data to all the snapshots. As a consequence, the snapshots are not static and writes to the origin are occasionally reflected to the snapshots. When there are multiple snapshots of the same origin volume with different chunk sizes, and you write to the origin volume, the data in the snapshots may be corrupted.This update ensures that the kernel driver always waits until all the chunks in all the snapshots are reallocated before dispatching a write request to the origin device.
- raid5: Mark cancelled readahead BIOS with -EIO. BZ#512552
1.88.10.1.9. Wireless Infrastructure and Driver Updates
- iwlwifi: Fix dual-band N-only use on IWL5x00. BZ#566696
- rt2x00: Fix work cancel race conditions. BZ#562972
- Update old static regulatory domain rules. BZ#543723
- Puma Peak wireless support. BZ#516859This update contains support for the iwl6000 hardware from Intel. Devices in this hardware line support 802.11a, 802.11b, 802.11g, and 802.11n protocols. This update also includes support for the iwl1000 hardware line. Support for iwl5000, iwl4965, and iwl3945 was also updated.In order to support the features of these drivers, the mac80211 and cfg80211 subsystems were updated. Further, all existing mac80211-based drivers were refreshed to match the updated mac80211 subsystem.
- Support Realtek RTL8187B wireless driver. BZ#514661
- Update Intel wireless driver (iwlagn) for iwl4965 / iwl5000. BZ#474328
- Add support for Atheros wireless ATH9k driver. BZ#456943The update of the mac80211 enabled support of the ath9k driver. This supports the full line of 802.11n wireless LAN adapters from Atheros.
- mac80211: fix reported wireless extensions version. BZ#513430
1.88.10.1.10. Memory Management Updates
- [Xen]
mmap()
with PROT_WRITE on Red Hat Enterprise Linux 5 was incompatible with Red Hat Enterprise Linux 4. BZ#562761 - A problem was found where
munmap()
would fail with an ENOMEM error if:- the number of VMAs = VMA limit - 1, and
- it does not unmap an entire VMA but only part of a VMA.
This update implements further checks to handle partial unmappings to avoid this problem. - Update
ioremap
to prevent kernel hang when using recent NVIDIA display drivers. BZ#549465A problem was found where attempting to run a recent NVIDIA display driver on 32-bit Red Hat Enterprise Linux 5.3 or 5.4 would cause the kernel to hang. This was due to hitting aBUG()
call in the__change_page_attr()
routine.This update provides the necessary changes to address this problem. - Prevent hangs during memory reclaim on large systems. BZ#546428
- Call
vfs_check_frozen()
after unlocking the spinlock. BZ#541956 - Display UID as well as PID in OOM killer output. BZ#520419
- Add a tracepoint for kernel pagefault events. BZ#517133This feature provides a tracepoint to trace kernel pagefault events. The argument should include the IP (instruction pointer) and the faulted virtual address.This update applies to 32-bit x86 and 64-bit Intel 64 and AMD64 architectures.
- Memory mapped files not updating timestamps. BZ#452129
- Prevent hangs or long pauses when zone_reclaim_mode=1. BZ#507360
1.88.10.1.11. Audit and Security Updates
1.88.10.1.11.1. Audit Updates
- Fix breakage and leaks in
audit_tree.c
BZ#549750A problem was found where if a user ranauditctl -R audit.rules
which unloads and then loads rules that include (for exeample) "-F dir=/var/log/audit" or "-F dir=/lib", it would result in a kernel OOPS.This update provides a fix for this issue. - Correct the record length of execve. BZ#509134
1.88.10.1.11.2. Cryptography Updates
- IBM S/390: Permit weak keys unless REQ_WEAK_KEY is set. BZ#504667
1.88.10.1.11.3. SELinux Updates
- Allow preemption between transition permission checks in order to prevent CPU soft lockup BZ#516216A problem was found where the kernel would sometimes go into a soft lockup for 10s at .context_struct_compute_av+0x214/0x39c. This update changes the way transition checks are performed in order to avoid this problem.
1.88.10.1.12. Miscellaneous Updates
- power_meter: Avoid OOPS on driver load. BZ#566575
- hvc_iucv: Allocate IUCV send/receive buffers in DMA zone. BZ#566202
- f71805f: Fix sio_data to
platform_device_add_data()
. BZ#564399 - Fix 32-bit Machine Check Exception Handler. BZ#562862
- Fix APIC and TSC reads for guests. BZ#562006
- zcrypt: Do not remove coprocessor in case of error 8/72. BZ#561067
- smsc47m1: Fix data to
platform_device_add_data()
. BZ#560944 - it87: Fix sio_data to
platform_device_add_data()
. BZ#559950 - w83627hf: Fix data to
platform_device_add_data()
. BZ#557172 - Power Now driver: fix crash on AMD family 0x11 processors. BZ#555180
- EDAC driver fix for non-MMCONFIG systems. BZ#550123
khungtaskd
not stopped during suspend. BZ#550014- Do not evaluate WARN_ON condition twice. BZ#548653
- Fix NULL pointer panic in acpi_run_os. BZ#547733
- Implement public pci_ioremap_bar function. BZ#546244
- Fix PTRACE_KILL hanging in 100% CPU loop. BZ#544138
- Fix compile warnings in eeh code. BZ#538407This update was necessary to address a compile problem in PowerPC introduced by a change in the PCI AER code.
- [infiniband] Fix bitmask handling from QP control block. BZ#561953
- [infiniband] Fix issue with sleep in interrupt ehca handler. BZ#561952
- [infiniband] Rewrite SG handling for RDMA logic. BZ#540686After dma-mapping an SG list provided by the SCSI midlayer, iser must ensure the mapped SG is "aligned for RDMA", in the sense that it is possible to produce one mapping in the HCA IOMMU which represents the whole SG. Next, the mapped SG is formatted for registration with the HCA.This update provides the necessary rewrites to achieve the above.
- [infiniband] init neigh->dgid.raw on bonding events. BZ#538067This update was necessary to address an issue found where, using IPoIB, connectivity would be lost with a single host but maintained with other hosts.
- USB driver update. BZ#537433This driver update avoids USB 1.1 device failures that may occur due to requests from USB OHCI controllers being overwritten if the latency for any pending request by the USB controller is very long (in the range of milliseconds).
- Add qcserial module to Red Hat Enterprise Linux 5 kernel. BZ#523888This module was added to support the Qualcomm WWAN cards used by some laptops.
- sysctl: Require CAP_SYS_RAWIO to set mmap_min_addr. BZ#534018
- Enable msi-x correctly on qlogic 2xxx series. BZ#531593This update enables the FC and FCoE drivers to use MSI-X or MSI interrupts when they are available. The ql2xenablemsix can be used to override this:
0 = enable traditional pin-based interrupt mechanism 1 = enable MSI-X interrupt mechanism 2 = enable MSI interrupt mechanism
- Implement futex priority-based wakeup. BZ#531552A problem was found where the threads waiting on the futex_q queue list would acquire the mutex lock in the order they were queued rather than by priority. This update addresses that problem.
- Make
scsi_dh_activate()
asynchronous to address the slower LUN failovers with large numbers of LUNs. BZ#537514 - [scsi] Fix inconsistent usage of
max_lun
BZ#531488 - Fix dlm_recv deadlock under memory pressure while processing GFP_KERNEL locks. BZ#530537
- [scsi] Panic at .ipr_sata_reset after device reset. BZ#528175
- [scsi] Export scsilun_to_int symbol. BZ#528153This symbol is needed by some drivers, and without this update they each tend to use their own copy of the entire function.
- Ensure pci_dev->is_enabled is set. BZ#527496Failure to set this may cause suspend/resume to fail on some devices.
- Fix a bug in
rwsem_is_locked()
function. BZ#526092 - [scsi] cciss: Ignore stale commands after reboot. BZ#525440
- Fix a mistake in ACPI debug statement that prevents kernel compilation. BZ#524787
- Fix panic in
cpufreq_get
on DL785-G6. BZ#523505A problem was found incpufreq_get
which sometimes causes a kernel panic on HP DL785-G6 machines running Red Hat Enterprise Linux 5.3 and 5.4.This update addresses the problem that was occurring and this kernel panic no longer occurs. - [FIPS140-2] Provide option to disable/enable use of the first random block. BZ#523259
- [FIPS140-2] Do not use the first n-bit block generated after power-up, initialization, or reset. BZ#522860
- thinkpad_acpi: Disable ecnvram brightness. BZ#522745The brightness of the screen needed to be manually set using the "Fn + Home" key combination every time you reboot an IBM T43 laptop, using the Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03). This problem was traced to the fact that the thinkpad_acpi CMOS NVRAM (7) and EC (5) did not agree on the display brightness level.This update addresses this problem and the screen now always starts at the highest brightness setting.
- pciehp: Fix PCI-E hotplug slot detection. BZ#521731A problem was found where the PCI-E hotplug slot was not detected by the pciehp driver on some platforms. The cause of this problem was traced to a bug in the pciehp driver. This update addresses this bug and PCI-E hotplug slots are now detected correctly.
- Fix NULL pointer dereference in
pci_bus_show_cpuaffinity()
BZ#519633A problem was found where reading/sys/class/pci_bus/0000:ff/cpuaffinity
(usingcat
or a similar function) would cause the kernel to crash and the system to reboot. This update provides a solution to this problem. - A problem was found with iommu=pt mode for intel_iommu where if you are using iommu=pt and you assign a device to a KVM guest and then de-assign it,the result is a device which is not usable in the host. It can be re-assigned to other guests again, but not directly used in the host.There is also an issue where with iommu=pt any PCI devices that are hot-plugged in the host cannot be used.This update provides a solution to the above problems.
- [firewire] fw-ohci: Fix IOMMU resource exhaustion. BZ#513827
- Support AMD Magny-Cours power-aware scheduler fix. BZ#513685
- Fix CPU llc_shared_map information. BZ#513684
- [cpufreq] Add option to avoid smi while calibrating. BZ#513649The CPU frequency (cpu_khz) was infrequently calculated as larger value than the CPU's specification in both Red Hat Enterprise Linux 5.1(x86) and 5.2(x86). This also contributed to the system time being gradually delayed. This update adds an option to avoid this problem.
- [cpufreq] Don't set policy for offline CPUs. BZ#511211
- Add CPU hotplug notifiers to support suspend-to-disk and suspend-to-RAM while using KVM. BZ#510814
- Better FASYNC handling on file close. BZ#510746
- fd leak if
pipe()
is called with an invalid address. BZ#509625 - Kernel panic occurs when adding nosmp option and booting the system. BZ#509581
- Increase hibernate timeout. BZ#507331
- Hang on boot due to wrong APIC timer calibration. BZ#503957
- DASD failfast flag cannot be set on. BZ#503222
- wacom: add Intuos4 support. BZ#502708
- st: display current settings of option bits. BZ#501030
- psmouse: reenable mouse on shutdown. BZ#501025
- Relocate initramfs to increase vmalloc space. BZ#499253
- Fix undefined reference to `__udivdi3'. BZ#499063
- Add Oprofile support for Nehalem-EP processors. BZ#498624
- Multiple device failure renders dm-raid1 unfixable. BZ#498532
- Don't oomkill when hugepage alloc fails on node. BZ#498510
- Prevent tmpfs from going readonly during oom kills. BZ#497257
- documentation: fix file-nr definition in fs.txt. BZ#497200
- Conditional flush in flush_all_zero_pkmaps. BZ#484683
- Fix corrupted intel_rng kernel messages. BZ#477778
- Use KVM pvclock code to detect/correct lost ticks. BZ#476075
- Fix mcp55 apic routing. BZ#473404
- Fix snapshot crash on invalidation. BZ#461506
- Add pci_domain_nr. BZ#450121
- LRO (Large Receive Offload) is a network technology that offloads some of the overhead associated with receiving high-volume traffic from a single host. Though there is a performance benefit to LRO it cannot be used in environments where the host will take the incoming traffic and forward it to another device on the system (internal or external). In such environments, the host will panic when LRO is enabled on an interface and that interface is placed into a bridge on the host.A check was placed in an additional portion of the bridge forwarding code and the following message (or similar) will be printed to the console or logs when a device with LRO enabled is placed into a bridge on the host or has routing enabled: "eth0: received packets cannot be forwarded while LRO is enabled". BZ#483646
- jbd slab cache creation/deletion is racey. BZ#496847
- In some cases, kernel panics while calling SysRQ-C. The printk warning about long delays was removed, and the kernel no longer hangs when SysRQ-C is called. BZ#497195
- Fix serial ports on IBM Point-of-Sale hardware. BZ#506799
- Add support for Intel multi-APIC-cluster systems. BZ#507333
- A bug was found in ia64_mca_modify_original_stack (arch/ia64/kernel/mca.c) where if INIT was issued while the kernel was in fsys-mode, the register was not saved in the stack. Consequently, the kdump corefile could not be backtraced in IA64. Registers in the stack are now restored on init. BZ#515753
- Add a tracepoint for the coredump event to the kernel. The new tracepoint provides tracing tools with pointers to the coredump filename string, and to the coredump_params data structure. BZ#517115
- Add four new signal-related tracepoints to the kernel. These tracepoints provide tracing tools which can deliver significant amounts of data. Refer to the bug report for full details. BZ#517121
- Add support for Nehalem-EX (Beckton) processors in Oprofile. BZ#521992
1.88.11. RHSA-2010:0610: Important kernel security and bug fix update
sprintf()
use were found in the Linux kernel Bluetooth implementation. Creating a large number of Bluetooth L2CAP, SCO, or RFCOMM sockets could result in arbitrary memory pages being overwritten. A local, unprivileged user could use this flaw to cause a kernel panic (denial of service) or escalate their privileges. (CVE-2010-1084, Important)
CIFSSMBWrite()
function in the Linux kernel Common Internet File System (CIFS) implementation. A remote attacker could send a specially-crafted SMB response packet to a target CIFS client, resulting in a kernel panic (denial of service). (CVE-2010-2248, Important)
mext_check_arguments()
function in the ext4 file system code. A local user could use this flaw to cause the MOVE_EXT IOCTL to overwrite the contents of an append-only file on an ext4 file system, if they have write permissions for that file. (CVE-2010-2066, Low)
possible circular locking dependency detected
warning was triggered. With this update, the warning is no longer displayed and the loading of a USB mass storage driver under kernel-debug works as expected. BZ#607483
bnx2x
network driver (10
Gb), TCP
bandwidth problems occurred, causing transfer rate slowdowns (down to 400
Kb) and network delays. The network traces shown that the reason for the TCP
bandwidth problems were TCP
delayed ACK mechanisms. This update improves the packet-handling code so that network ACKs are not delayed when using TPA, GRO (Generic Receive Offload), or LRO (Large Receive Offload) with the bnx2x
driver, thus leading to increased networking performance. BZ#613900
/var/log/messages
directory during IO runs. With this update, the firmware dump errors no longer appear in the /var/log/messages
directory. BZ#613688
CNIC
driver, occasionally, data structures were freed when the device was down. If at that moment an ISCSI
netlink message was received, a crash occurred. With this update, the crash no longer occurs. BZ#615260
acpiphp
module (using the /sbin/modprobe
command) on a Intel Xeon processor 7500 series system caused kernel panic. With these updates, an error message is produced when the aforementioned case occurs and the machine does not panic. BZ#607486
1.88.12. RHSA-2010:0723: Important kernel security and bug fix update
ecryptfs_uid_hash()
function in the Linux kernel eCryptfs implementation. On systems that have the eCryptfs netlink transport (Red Hat Enterprise Linux 5 does) or where the /dev/ecryptfs
file has world writable permissions (which it does not, by default, on Red Hat Enterprise Linux 5), a local, unprivileged user could use this flaw to cause a denial of service or possibly escalate their privileges. (CVE-2010-2492, Important)
msleep()
calls with the MDELAY()
macro and handles the locking properly. BZ#620661
msi_nolock
, which allows for better simultaneous processing of MSIs. BZ#621940
mmap()
or munmap()
function on /dev/zero
decreased the performance on multiple threads. This update allows the user to switch off the optimization by typing echo 0 > /proc/sys/vm/vm_devzero_optimization
at a shell prompt as superuser. BZ#623141
/proc/cpuinfo
when running a kernel-xen kernel. This has been fixed, and /proc/cpuinfo
now contains all CPU flags as expected. BZ#624365
ccw_device_set_options()
in dasd_generic_probe()
unset the CWDEV_ALLOW_FORCE flag set in dasd_eckd_probe()
and the unconditional reserve was not allowed on ECKD dasds. This update sets flags only in discipline specific probe functions. BZ#627194
1.89. kexec-tools
1.89.1. RHBA-2009:1600: bug fix update
Note
1.89.2. RHBA-2010:0179: bug fix update
1.90. krb5
1.90.1. RHSA-2010:0029: Critical security update
Important
1.91. ksh
1.91.1. RHBA-2009:1686: bug fix update
Note
1.91.2. RHBA-2010:0234: bug fix and enhancement update
1.92. ktune
1.92.1. RHBA-2009:1422: bug fix update
Note
1.92.2. RHBA-2010:0238: bug fix and enhancement update
1.93. kudzu
1.93.1. RHBA-2010:0191: bug fix and enhancement update
1.94. kvm
1.94.1. RHBA-2009:1423: bug fix update
Note
1.94.2. RHBA-2009:1488: bug fix update
Note
1.94.3. RHBA-2010:0158: bug fix update
Note
1.94.4. RHSA-2010:0271: Important security, bug fix and enhancement update
- Setting the
cpu_set
variable to1 online
in the qemu Monitor and then shutting down the guest would cause the host or the guest to crash. The updated package resolves this issue and prevents the host or guest from crashing in this scenario. (BZ#487857) - The KVM configure script would not abort if the correct options were not enabled. The KVM configure script now verifies features are enabled or disabled by the configure script and aborts if the features was not loaded as requested. (BZ#489900)
- The para-virtualized network drivers (
virtio-net
) lacked non-maskable interrupt (NMI) injection masking on AMD-based hosts. This caused Windows XP guests using the para-virtualized network driver could fail with a Blue Screen error during certain tests. The updated packages resolve this issue. (BZ#492290) - Timer events were processed before entering guest mode. This meant that certain timer events may not have been processed. Timer events are now processed in the main VCPU event loop so timer events are processed while the VCPU is halted. Timer events may inject interrupts or non-maskable interrupt (NMI) which will then unhalt the VCPU. This fixes the issue of unconditionally unhalting the VCPU. (BZ#492663)
- If one or more VCPUs was disabled, VCPUs would appear in Windows Server 2008 Device Manager as devices with the ! symbol indicating an error. Windows does not handle CPUs marked as present (bit 0 in ACPI spec), but not enabled (bit 1), which causes this issue.However, there are situations where Linux expects CPUs to be present but not enabled. This is a heuristic test used by Linux to determine if a CPU is hot-pluggable.The updated package fixes virtualized CPU detection for Windows but breaks the ability to hot-add CPUs into Linux guests. (BZ#495844)
- Using the numeric keypad of a keyboard with or without Num Lock produced erroneous input on guests accessed with VNC through the QEMU monitor application. The number pad keys should now work for input on guests accessed with VNC. (BZ#497507)
- An unhandled interrupt from the kvm_vcpu_block() call unhalted a VCPU outside of the interrupt window. As a consequence, when the "
there is no bootable disk
" error presented the qemu process used 100% of the available CPUs. The updated packages resolve this issue and the interrupt is now handled correctly. (BZ#502086) - Windows Server 2008 R2 guests would hang after a restart if the guest was created with multiple VCPUs. This was caused by not properly filtering non-maskable interrupts (NMIs) from the guests during the restart procedure. The updated packages fix this issue and Windows Server 2008 R2 guests can successfully use multiple VCPU. (BZ#502543 BZ#503322)
- Migrating a paused guest caused the guest to resume at the destination. Paused guests now remain paused after a migration. (BZ#503367)
- Multiple virtualized guests using the hypercall device resulted in one or more of the guests using 100% of their assigned CPUs or becoming unresponsive. The updated packages fix the hypercall device, preventing this issue. (BZ#503759)
- VCPUs were not reported correctly to Windows XP guests. On the Windows XP guest the number for CPUs listed in Task Manager was lower than the number of CPUs assigned to the guest. Windows XP guests should now use and display the number of VCPUs assign if the guest can handle that number of CPUs. (BZ#508040)
- A segmentation fault occurred when a guest used a
i82551
emulated network interface card was used. The segmentation fault is fixed in the packages. (BZ#510706) - Creating guests that use both 64k and 4k image block cluster sizes and virtualized IDE as the storage device driver would cause a segmentation fault in the
qemu-kvm
process. The updated packages resolve this issue. (BZ#542923) - Running the
migrate_set_speed
command in the QEMU console after runningmigrate_cancel
causes segmentation fault in KVM. The updated packages fix this issue and the code causing the segmentation fault is fixed. (BZ#522887) - A segmentation fault occurred when using the
qemu-img rebase
command to rebase an image snapshot. (BZ#563141) - The
qemu-img rebase
command failed with an "Operation not supported" error message when it was run on locally-attached block devices. (BZ#569762) - The
qemu-img
command failed to copy a RAW image to a Fibre Channel storage device. Theqemu-image
command can now copy, convert and create images on Fibre Channel storage devices. (BZ#511072) - Storage I/O errors were processed out of order causing the guest to change state or crash unexpectedly. The guest state handlers now process storage I/O errors in the proper order. (BZ#514522)
- A guest would occasionally not accept keystrokes or mouse clicks after rebooting. The updated package resolves this issue and user interactions are accepted after repeatedly rebooting guests. (BZ#515275)
- In rare instances, certain virtualized guests could lock up while requesting a
raw_pread
system call. The offset was larger than the file size of the read failures which causes the system to infinitely loop I/O requests. This could, in certain circumstances lead to file system corruption on virtualized guests. The updated pacakges add a result test which prevents the infinite request loop. (BZ#515655) - The guest could change the QXL device ROM which could result in memory corruption. The updated packages prevent the guest from modifying the QXL device ROM. (BZ#537888)
- The MRS storage array (
msrs
) inkvm_arch_save_regs()
function. The array was sized too small for the function and may cause stack corruption. (BZ#528917) - Incorrectly handled I/O errors could cause guests file system corruption when using the para-virtualized block drivers and IDE emulation of NFS storage. The updated packages resolve this issue and host I/O errors will pause the guest instead of causing file system corruption. (BZ#531827)
- With Red Hat Enterprise Virtualization, the
virtio_blk_dma_restart_bh()
function previously handled write errors. The function was not updated for this, causing read errors to be resubmitted as writes. This caused guest image corruption in some cases.Additionally, the return values of thebdrv_aio_write()
andbdrv_aio_read()
functions were ignored. If an immediate failure occurred in one of these functions, errors would be missed and the guest could hang or read corrupted data. (BZ#552487) - with Red Hat Enterprise Virtualization, guests continued to run after encountering disk read errors. This could have caused guest file systems to corrupt (but not the host's), notably in environments that use networked storage. With this update, the
qemu-kvm
command's-drive "werror=stop"
option now applies not only to write errors but also to read errors. When using this option, guests will pause on disk read and write errors.By default, guests managed by Red Hat Enterprise Virtualization use the"werror=stop"
option. This option is not used by default for guests managed by libvirt. (BZ#533390) - KVM would crash or fail to boot when attempting to assign 64GB of memory to 32-bit guests using PAE. KVM now supports addressing up to 48 bits of physical memory with PAE. (BZ#516545)
- Windows Server 2003 32-bit guests assigned more than 4GB of RAM would crash after rebooting the guest. The updated packages resolve this issue and Windows Server 2003 32-bit guests can be assigned more than 4GB of RAM. 32-bit guests may not be able to use more than 4GB of RAM, refer to the guest operating system's documentation. (BZ#516762)
- When using the virtual
vm8086
mode, bugs in the emulated hardware task switching implementation may have caused older guest operating systems to malfunction. (BZ#517324) - An "
unhandled vm exit: 0x31 vcpu_id 0
" error message could appear when installing certain guest operating systems, such as SUSE Linux Enterprise Server 11, using a para-virtualized block device (virtio-blk). The updated packages resolve this issue and installation with the para-virtualized drivers is supported and working. (BZ#518081) - The
__kvm_mmu_free_some_pages
list was not verified empty before it was used. The updated package verifies the__kvm_mmu_free_some_pages
list is empty before attempting to look at list entries. (BZ#519397) - Windows Server 2008 64 bit guests use a
cr8
call which executed avmexit
call. This caused performance issues for Windows Server 2008 guests. The updated packages use a different call method to handlecr8
calls which significantly improves the performance of Windows Server 2008 64 bit guests. (BZ#520285) - When attempting to resume from hibernate with Windows Server 2003 guests, KVM would attempt to stop the QEMU emulated audio device which was not activated. This caused a "
snd_playback_stop: ASSERT playback_channel->base.active failed
" error message to appear and the resume process to fail and the guest to crash. The updated package resolves this issue. (BZ#520394) - Time drift may have occurred in Windows guests that use the IOAPIC interrupt for timing. The updated packages resolve this issue and Windows guests should now keep time accurately. (BZ#521025)
- Windows Server 2003 (32-bit and 64-bit) guests may have experienced time drift. (BZ#543137)
- On AMD hosts, Window Server 2008 R2 Datacenter guests would stop during the installation at the step "
Setup will continue after restarting your computer
". This issue is resolved and Windows Server 2008 R2 Datacenter guests now successfully install. (BZ#521749) - Resetting the PCI status of a para-virtualized network device (virtio-net) would cause KVM to crash. This issue is resolved the the updated packages. (BZ#521829)
- The German keyboard map was missing some keys in when accessing a guest with VNC. The German keyboard map now contains all keys when accessing guests with VNC. (BZ#521835)
- When a guest issued an Inter-processor Interrupt (IPI) call, the call would cause KVM to issue a global IPI call on the host. The global IPI call interrupts all processors instead of just those assigned to the guest. The updated packages resolve the issue by using the kernel's IPI handling functions instead of emulating the IPI handler. (BZ#524970)
- KVM and virtualized guests would become unresponsive due to waiting infinitely for an
aio
threads to return. The updated packages resolve this issue by correctly timing out threads which do not return. (BZ#525114) - The host KVM process could crash or use 100% of the allocated CPUs when a guest with more than one VCPU received high volumes of network traffic through a device using the para-virtualized network drivers (virtio-net). This issue is resolved in the updated packages. (BZ#525323)
- KVM did not change the pacakge address of the etherboot
.zrom
file. KVM would always used the default, thene.zrom
file. Guests could not get an IP address or access PXE servers. The updated packages resolve this issue and guests can access PXE server when using non-default network devices. (BZ#526124) - KVM could generate invalid memory types in Memory Type Range Registers (MTRR) and Page Attribute Tables (PAT). This could be used by guests running random code to possibly store (and later use) a random MTRR type. The updated package prevent these invalid memory types from being created. (BZ#526837)
- An error in the Makefile prevented users from using the source RPM to install KVM. (BZ#527722)
- Linux guest
initrd
images greater than 4GB would cause the guest to crash. KVM now limits the size ofinitrd
images to less than 4GB. (BZ#529694) - If the
qemu-kvm
command's-net user
option was used, unattended Windows XP installations would not receive an IP address after rebooting. The guest requests a second DHCP address which makes the list of free DHCP addresses run out much quicker. This issue is fixed by reassigning the same addressed requested with DHCP to the guest after the guest reboots. (BZ#531631) - The para-virtualized clock (pvclock) Mode-specific register values were not preserved after a migration. This issue also affected the para-virtualized clock when a guest was saved and restored. These drivers not being saved could cause the guest's time keeping to become significantly skewed after restoring or migrating the guest. In the updated packages, the MSR values are preserved when a guest is saved and restored, and for migrations. (BZ#531701)
- Installing Windows Server 2008 R2 from an ISO image could result in a blue screen "
BAD_POOL_HEADER
" stop error. (BZ#531887) - Running certain test functions on Windows 7 guests caused a blue screen "
HAL_RTC_IRQF_WILL_NOT_CLEAR
" stop error. (BZ#556455) - Windows Server 2003 R2 Service Pack 2 32-bit guests using the para-virtualized block drivers could crash with an
unhandledvm exit
error during reboot. The hypervisor now handles this error, resolving the issue. (BZ#532086) - After restoring a migrated Windows Server 2008 R2 guest, a race condition caused the guest to hang during the shut down sequence. The updated packages resolve this issue and Windows Server 2008 R2 guests will successfully shut down when requested after a migration. (BZ#533090)
- a bug in the
grow_refcount_table()
error handling caused infinite recursion in some cases. This caused theqemu-kvm
process to hang and eventually crash. (BZ#537075) - Full I/O error codes were not passed up to the host or the Red Hat Enterprise Virtualization Manager. Accurate I/O error codes are now forwarded to the user and management tools. (BZ#537077)
- There was a regression in the
qemu-img
command, Fibre Channel devices could not be formatted using RAW or use preallocated RAW devices. Theqemu-img
command is updated to handle Fibre Channel devices in the RAW format. (BZ#537655) - Guests could not eject CD-ROMs from physical CD-ROM drives attached to the guest. The updated packages resolve this issue and guests can now eject CD-ROMs from physical CD-ROM drives. (BZ#539250)
- The
qcow2
file format unnecessarily rounded up the length of the backing format string to the next multiple of 8. The array inBlockDriverState
can only store 15 characters, causing backing formats with 9 characters or more to fail. This issue effected devices using thehost_device
format. The updated packages resolve this issue by determining the length of the backing format ofqcow2
devices. (BZ#540893) - Migrations could fail due to invisible physical CPU states. A new set of IOCTL exports report user-invisible states related to exceptions, interrupts, and Non-Maskable Interrupts (NMIs). These functions allow management tools to prevent this type of failed migration. (BZ#541084)
- The KVM process could become non-responsive if a networked or local connect to the QXL driver was lost while the driver was running. This cause a "
qxl_display_update: waiting for command
" error message to be printed in the logs. The updated packages resolve this issue. (BZ#544785) - The
qemu-kvm
man page incorrectly described theqcow2
default ascache=writeback
. The default iscache=none
forqcow2
images andcache=writethrough
for all other disk types. The man page forqemu-kvm
has been updated to reflect this. (BZ#545194) - KVM did not verify if barriers were required for migration. KVM now verifies if barriers are required for guest migration and disables barriers if they are not required. (BZ#549938)
- The hypercall driver for Windows guests did not reset the device when the guest was shut down or rebooted. This occasionally caused the driver to use 100% of the CPU and cause the guest to hang. (BZ#550755)
- The
kvm-qemu-img
command failed to convert sparse RAW image files to qcow2 sparse snapshot image files. (BZ#558195) - Migration with the
-M rhel5.5.0
parameter did not work for migration to or from Red Hat Enterprise Linux 5.5. Migration with the-M
parameter is now supported and functional. (BZ#559163) - Removed a warning message which appeared when the
-initrd
option was used. (BZ#512672) - The KVM kernel module would panic if the
paging64_sync_page()
call was executed on a system using PCI passthrough devices. This kernel panic error could occur if a guest with an attached PCI device was started. The updated packages resolve this issue. (BZ#566385) - Removed a debugging message
qemu_popen: returning result of qemu_fopen_ops
that displayed when saving a virtualized guest state into a compressed file. (BZ#530533)
- The KVM hypervisor does not accept
MSR_KERNEL_GS_BASE
intercept calls for Windows Server 2008 guests. This improves performance of Windows Server 2008 guests under heavy loads. (BZ#488130) - qcow2 now uses 64Kb as the default block cluster size instead of 4Kb blocks which improves performance for guests using qcow2. (BZ#502809)
- Various unsupported features of the
qemu-kvm
command are now compiled out of the kvm pacakges. (BZ#516672) - Support for migration from older hypervisors which use versions of savevm with additional fields which are not supported by newer versions. This feature is required for migrations from older hypervisors to newer versions of KVM. (BZ#541731)
- Support for guest access to advanced CPU extensions, including: SSE4.1, SSE4.2 and SSE4a. (BZ#518090)
- SMBIOS table 4 data is now generated for Windows guests. (BZ#537178)
- The cache flushing command was changed from
fsync
tofdatasync
. This allows write caches to be exposed to guests and allows the guest to request for flushing I/O buffers. This improves I/O performance for some guests. (BZ#537646) - Support for changing the file format of an in-place backing file. (BZ#530134)
- Support for Red Hat Enterprise Linux 3.9 guests running the para-virtualized drivers. (BZ#536749)
- The QXL driver now supports setting resolutions of 1024x576 and 1024x600. (BZ#552240)
1.95. less
1.95.1. RHBA-2010:0214: bug fix and enhancement update
1.96. libXi
1.96.1. RHBA-2010:0127: bug fix update
Note
1.97. libXrandr
1.97.1. RHBA-2009:1608: bug fix update
Note
1.98. libXt
1.98.1. RHBA-2010:0192: bug fix update
1.99. libaio
1.99.1. RHBA-2010:0277: bug fix update
1.100. libcmpiutil
1.100.1. RHBA-2010:0222: bug fix and enhancement update
1.101. libevent
1.101.1. RHEA-2010:0244: enhancement update
1.102. libgnomecups
1.102.1. RHBA-2009:1577: bug fix update
Note
1.103. libgtop2
1.103.1. RHBA-2010:0099: bug fix update
Note
1.104. libhugetlbfs
1.104.1. RHEA-2010:0056: enhancement update
Note
1.105. libsepol
1.105.1. RHBA-2010:0183: bug fix update
1.106. libuser
1.106.1. RHBA-2009:1525: bug fix update
Note
1.107. libvirt
1.107.1. RHBA-2009:1424: bug fix update
Note
1.107.2. RHBA-2010:0205: bug fix and enhancement update
libvirt
packages that fix several bugs and introduce feature enhancements are now available for Red Hat Enterprise Linux 5.
- On Xen guests, the netfront and RTL8192 network drivers could run concurrently, bringing up two network interfaces where only one was configured. The two interfaces would share the same MAC address and could cause networking difficulties. Support for a netfront interface model has been added, meaning only the single netfront interface is configured.
- The storage pool deletion routine did not distinguish between files and directories when removing data. As a result, inactive storage pools could not be deleted. With this update, files and directories are removed appropriately, allowing inactive storage pools to be deleted.
- When adding a new physical host PCI device,
libvirt
would not attempt to reset the PCI bus if other functions or devices were present on the same bus. Some PCI devices could not utilized for virtualization as a result. Attempts to reset the PCI bus will now be made, allowing affected devices to be used for virtualization. - Devices attached to a guest in managed mode were not automatically re-attached to the host OS when the guest shut down. Manual intervention was required to use these devices again when the guest is re-started. Managed mode devices will now be re-attached to the host when the guest shuts down, allowing them to be automatically used when the guest is re-started..
- The Xen driver was not checking that guest domains with the same UUID also had the same name. Using the
virsh edit
command to change the name of a Xen domain would make a new copy of the configuration file with the new name, but not alter the original configuration file. UUIDs and names for guest domains are now checked to ensure they match. Attempting to change the name of a domain using thevirsh edit
command will now return an error message and not make any change to the system. - Valid values for the credit scheduler parameter are in the range
0
-65534
. A value of65535
was being accepted as valid, but would not alter the scheduler configuration. With this release, only values within the valid range are accepted. - Using the
info
command to change memory values on a KVM guest showed that inactive KVM guest memory was not being reported correctly. Memory reporting for unused domains was corrected in theqemu
driver and the info command now returns the correct value. - Running the command
virsh vol-key volname
was sometimes resulting in a segmentation fault. A change was made to the way pool objects are handled and the key lookup no longer crashes. - Using the pool parameter with the
virsh vol-path
command would result in errors. Thevirsh vol-path
command was altered to support the pool parameter and the errors no longer occur. - The
virsh find-storage-pool-sources
command failed to find anydir/nfs/netfs
pool sources and failed withunknown failure
. The error reporting was fixed and the command now works as expected. - The
virsh nodedev-create
command resulted in an out of memory error. This was found to be a false positive. The checks were updated, and the error now only occurs if there is an actual memory problem. - Two different methods were using the same name for different
libvirt
entry points, which created a device error when creating nodes. One of the methods was renamed and node creation now works as expected. - Running the
virsh nodedev-destroy
command to destroy a NIC interface causedlibvirtd
to hang indefinitely. The locking issue was found and rectified and thelibvirtd
crash no longer occurs. - Running the
virsh vol-delete
command produced afailed to connect to the hypervisor
error andlibvirtd
needed to be restarted. The code was altered to refresh allocation and permissions information, but not capacity information, and the command now works as expected. - When an XML configuration file was generated using
virsh dumpxml
for a running virtual machine, it contained parameters used for backwards compatibility with previous versions.virt-xml-validate
would report that the generated file was not valid because of these legacy parameters. The validate program was altered to accept the parameters used in the generated XML file, which now validates correctly. - Running concurrent TLS connections under the
libvirt
python wrapper causedlibvirt
to crash. Changes were made to the way thatGNUTLS
handles threading and the crash no longer occurs. libvirt
was not reporting current vCPU and pCPU placement or the vCPU execution time counter accurately. The behavior was changed so thatlibvirt
doesn't find out the affinity when set withtaskset
, but does when set withvirsh vcpupin
. The reporting is now correct.- Creating npiv devices works as expected, but puts error messages into the
/var/log/messages
file. The Opened WWN path/sys/class/fc_host//host5/port_name
for reading message was updated and the error messages no longer appear in the log file. - The
virsh
man page described “most operations” as being asynchronous, which is not the case. The man page was updated to state that most operations are synchronous except creation and shutdown of domains. - Guests that use the default source clock try to compensate for lost ticks by reading the TSC as well. This can cause the guest clock to go out of synchronization. All Red Hat Enterprise Linux guests now unconditionally add
--no-kvm-pit-reinjection
to theqemu
command line, and the guest no longer falls out of synchronization. libvirt
would not perform a power management reset if there were other functions on the device. The PCI Power Management reset only affects individual functions, and not the whole device. The check for other functions was removed, so that where both are available, the whole device reset is preferred over individual function resets.- When a migration was performed to a virtual machine that had been paused, the virtual machine would no longer be paused after the migration had completed. The behavior of
qemu-kvm
was changed so that it no longer 'forgets' the virtual machine is paused, and it will now stay paused during a migration. libvirt
was ordering disks unecessarily. When a new disk was added, it would sometimes shift the boot disk later in the list, causing the user to be unable to boot. The sorting algorithm was changed, and will now insert a new disk as far to the end of the list as possible, while being ordered correctly with other disks on the same bus. This resolved booting errors caused by disk ordering.- A typographical error in an XML domain file caused
libvirtd
to suffer a segmentation fault. A check was added, and a typing mistake will now causelibvirtd
to fail gracefully and produce a meaningful error report. - Devices that are assigned below a non-ACS switch can cause transactions to bypass the VT-d hardware and the validation process.
libvirt
now successfully blocks devices between non-ACS switches, unless the user specifies the permissive='yes' attribute for <hostdev>, so all transactions now undergo validation by default. - When querying Xen remotely virsh would sometimes raise an "unknown failure" error. The semantics were modified and where possible, the error is now more informative.
- When using
xen+ssh://
to connect to a host, sometimes an RPC entry point would not be available anddominfo
would raise an uninformativeerror: unknown procedure
error. The error reporting was changed and it now reports as an unsupported entry point. - When a network created a bridge, it would only be enabled if the host had an IP on that bridge. This would cause the bridge creation to fail quietly, and packets would not be passed as expected. The error messages were improved for bridge creation and deletion, and if a failure occurs, it will now produce an informative error.
- HVM VT-d PCI passthrough attach and detach was not working correctly and devices could not be hotplugged. The attach and detach code now has additional checks and hotplugging functions as expected.
- When
virt-manager
tried to attach a PCI device to a Xen guest, it calledvirNodeDeviceReset
and subsequently crashed. The Xen driver was updated, and it now checks if a given PCI device is assigned to another guest, so that PCI devices can be attached as expected. - When the host was running the KVM hypervisor, the
libvirtd
process was occasionally unable to connect to the hypervisor. In this case,qemu-kvm
failed to start, and gave a false NUMAout of memory
error. The error handling was changed so that NUMA errors are now non-fatal. Errors are now logged, and connection progresses as expected. libvirt
was found to be incorrectly detecting machine types supported by KVM. This meant that KVM guests which did not specify any machine type could not be created. This also caused some rare problems that would cause/distribution/virt/install
to fail.libvirt
was updated to correctly detect and identify KVM-supported machine types.
- Support has been added for assigning Single Root I/O Virtualization (SR-IOV) devices to
qemu
guests. - Implementation of the
virsh dump
command for QEMU/KVM guests is included in this release. - Support was added to
libvirt
for KVM PCI device assignment hotplug. - Added
-mem-prealloc
to the KVM command line when using hugepage. libvirt
now allows the creation of more than 256 guests, and more than 150 DHCP leases.- The
-M rhel5.4
arguments are now passed by default when launchingqemu-kvm
. This improves backward migration ability.
libvirt
are advised to upgrade to these updated packages, which resolve these issues and add these enhancements.
1.108. libvirt-cim
1.108.1. RHBA-2009:1421: bug fix update
Note
1.108.2. RHBA-2010:0206: bug fix and enhancement update
1.109. libvorbis
1.109.1. RHSA-2009:1561: Important security update
Important
1.110. linuxwacom
1.110.1. RHEA-2010:0325: enhancement update
1.111. lm_sensors
1.111.1. RHBA-2010:0186: bug fix and enhancement update
1.112. log4cpp
1.112.1. RHEA-2010:0313: enhancement update
1.113. logwatch
1.113.1. RHBA-2010:0033: bug fix and enhancement update
Note
1.114. lvm2
1.114.1. RHBA-2009:1476: bug-fix update
Note
1.114.2. RHBA-2009:1538: bug-fix update
Note
1.114.3. RHBA-2010:0298: bug fix and enhancement update
1.115. lvm2-cluster
1.115.1. RHBA-2009:1475: bug-fix update
Note
1.115.2. RHBA-2010:0299: bug fix and enhancement update
1.116. man-pages
1.116.1. RHBA-2009:1574: bug fix update
Note
1.117. man-pages-ja
1.117.1. RHBA-2009:1630: bug fix update
Note
1.118. mcelog
1.118.1. RHBA-2010:0247: bug fix update
1.119. mdadm
1.119.1. RHBA-2010:0006: bug fix update
Note
1.120. mesa
1.120.1. RHBA-2010:0261: bug fix update
1.121. metacity
1.121.1. RHBA-2009:1610: bug fix update
Note
1.121.2. RHBA-2010:0245: bug fix and enhancement update
1.122. microcode_ctl
1.122.1. RHEA-2010:0243: enhancement update
1.123. mkinitrd
1.123.1. RHBA-2010:0295: bug fix and enhancement update
mkinitrd
utility creates file system images for use as initial ramdisk (initrd) images.
- booting a Storage Area Network (SAN) from a replicated Logical Unit Number (LUN) following a loss of the primary site would fail when doing array-based synchronous data replication to a remote site. This was due to the fact that the initrd on the replicated LUN is configured to see the World Wide Identifier (WWID) of the primary LUN only. A patch has been applied that allows for the creation of all multipath devices so that the replicated LUN is visible for booting. It should be noted that some manual configuration is required following the installation of the updated package:
- ensure that
multipath.conf
has the correct stanzas for both multipath devices. - run
mkinitrd
again.
A replicated LUN will now successfully boot provided:- the
multipath.conf
in the initrd does not blacklist the new LUN and; /var/lib/multipath/bindings
in the initrd is either empty or contains an entry binding mpath0 (or the device originally installed to) to the replicated LUN's WWID.
scsi_model devflag
options appended to/etc/modprobe.conf
can be of the form: “options scsi_mod dev_flags="HITACHI:OPEN-9 -SUN:0x240” to specify more than one SCSI model. These strings are written as arguments to theinsmod
command within theinitrd
script. The leading spaces of the second model name in the above example were incorrectly read as a single space by thenash
command resulting in the/proc/scsi/device_info
file containing invalid strings. A user specifying a SCSI model in this way would have to manually edit the/proc/scsi/device_info
file as a result. A patch has been applied tonash.c
to correctly handle the quoted string following thedev_flag
argument. The string is now written to the/proc/scsi/device_info
file in the correct format. (BZ#467850)mkinitrd
uses a global variablerootdev
to store the name of the root device. This is either auto-detected or passed in via the command line--rootdev=
parameter. Changes applied tomkinitrd
to supportboot from multipath
introduced the localrootdev
variable. This variable overrides the global variable resulting in an incorrect root device, such as a component SCSI device, being written to the/init
script preventing the system from booting. The local variable has been renamed to avoid the conflict. Runningmkinitrd
on a multipath boot system now results in a successful boot of the system. (BZ#503567)mkinitrd
runsnash
on each logical volume. Theblock_find_fs_by_key()
method calls thenashDmGetDevName()
method for each logical volume. Thenash
command does not run to completion in a reasonable time-frame as thenashDmGetDevName()
recurses through all devices each time it is called. This update allowsnashDmGetDevName()
to cache its results, sonash
no longer uses 100% of the CPU when installingRPM
s. (BZ#516047)mkinitrd
copied thelvm.conf
file verbatim to the initrd without parsing it properly. If the logical volume manager (LVM) was configured to use host tags, Red Hat Enterprise Linux would not boot because a host name could not be set at initrd time.lvm --dumpconfig
is now used to retrieve the LVM configuration file. (BZ#517868)mkinitrd
attempted to explicitly activate the subsets of a nested RAID 10 set. Error messages would then be printed to the log during boot. These messages could safely be ignored. They have now been removed to avoid confusion. (BZ#526246)mkinitrd
copied the symbolic link of a bootpath driver instead of the actual bootpath driver. This caused kernel panic due to an unavailable driver on first boot of the operating system.mkinitrd
now checks the full path of symbolically linked drivers. (BZ#540641)- when the root file system was on the logical volume manager (LVM), as is the default installation option,
nash
received a segmentation fault reference if some modules did not load during post-installation reboot. This caused unwarranted kernel panic. Kernel panic no longer occurs as a result of the non-loading of modules. (BZ#560567) - several virtio modules were missing from the previous version of
mkinitrd
. This meant thatmkinitrd
built incorrectly upon installation if virtio block or network devices were used within the Kernel Based Virtual Machine (KVM). The final result was kernel panic. These updated packages contain the required modules which allowmkinitrd
to build and install correctly. (BZ#560672)
- the
scsi_dh_rdac
module is needed to support many LSI Engenio based (IBM and non-IBM) storage devices. With the inclusion of a module such as thescsi_dh_rdac
module in initrd, the time to boot a system with multiple rdac devices is minimized. A patch has been applied tomkinitrd
to load everyscsi_dh_*
module in the event that multipath devices are detected. The patch currently succeeds in loadingxscsi_dh_rdac
modules for installations on DS4K storage and further work is being undertaken to ensure the successful loading of modules independent of the host device. (BZ#460899) mkinitrd
is responsible for ensuring that all drivers, applications, and configuration information needed to mount the root filesystem are packaged into each kernel's initrd. Unlike the Logical Volume Manager (LVM) component ofmkinitrd
, multipath operates on only the logical volume associated with the root filesystem and not the volume group containing the root filesystem. As a consequence, when installing a system with multipath devices, only disks currently in use by the root's logical volume have multipath configured within the initrd. A patch has been applied that wraps thefind_mpath_deps
in a loop that iterates through every primary volume in the root volume group. Non-LVMs are handled in a separate case by runnningfind_mpath_deps
against the root device. Installing a system with multipath devices will now result in the primary volumes in the root virtual group being on multipath devices. (BZ#501535)
1.124. module-init-tools
1.124.1. RHBA-2010:0242: bug fix update
1.125. mtx
1.125.1. RHBA-2009:1607: bug fix update
Note
1.126. mysql
1.126.1. RHBA-2009:1693: bug fix update
Note
1.126.2. RHSA-2010:0109: Moderate security update
Important
1.127. nautilus-open-terminal
1.127.1. RHBA-2009:1483: bug fix update
Note
1.128. neon
1.128.1. RHSA-2009:1452: Moderate security update
Important
1.129. net-snmp
1.129.1. RHBA-2009:1437: bug fix update
Note
1.129.2. RHBA-2010:0253: bug fix and enhancement update
1.130. net-tools
1.130.1. RHBA-2009:1677: bug fix update
Note
1.131. NetworkManager
1.131.1. RHSA-2010:0108: Moderate security update
Important
1.131.2. RHBA-2010:0263: bug fix update
1.132. newt
1.132.1. RHSA-2009:1463: Moderate security update
Important
1.132.2. RHBA-2009:1482: bug fix update
Note
1.133. nfs-utils
1.133.1. RHBA-2010:0284: bug fix update
1.134. nspluginwrapper
1.134.1. RHBA-2010:0187: bug fix update
1.135. nss_ldap
1.135.1. RHBA-2009:1527: bug fix update
Note
1.135.2. RHBA-2010:0260: bug fix update
1.136. numactl
1.136.1. RHBA-2010:0319: bug fix update
1.136.2. RHBA-2009:1626: bug fix update
Note
1.137. openCryptoki
1.137.1. RHBA-2009:1685: bug fix update
Note
1.138. openais
1.138.1. RHBA-2009:1474: bug fix update
Note
1.138.2. RHBA-2010:0180: bug fix update
1.139. OpenIPMI
1.139.1. RHBA-2009:1487: bug fix update
Note
1.139.2. RHBA-2009:1629: bug fix update
Note
1.140. openib
1.140.1. RHBA-2010:0292: bug fix and enhancement update
1.141. openldap
1.141.1. RHSA-2010:0198: Moderate security and bug fix update
1.142. openmotif
1.142.1. RHBA-2010:0132: bug fix update
Note
1.143. openoffice.org
1.143.1. RHBA-2010:0274: bug fix and enhancement update
- a nested table would be removed from the defined nesting structure when rendered in Web Layout view causing OpenOffice.org to crash. A patch has been applied to ensure the correct rendering of nested tables. (BZ#469157) (BZ#469157)
- using OpenOffice.org Impress in a dual monitor configuration and selecting Slide Show → Slide Show would cause the application to crash as the application was configured to return a default screen. A patch has been applied to detect and return the monitor upon which the slide show will be displayed. (BZ#476949)
- when saving a html document containing cells which are merged across rows, OpenOffice.org Writer would insert an additional cell in each row of the spanned set. When the document was rendered, the cells would appear to be misaligned due to the creation of the additional cells. A patch has been applied to retain the original table row span configuration. (BZ#491357)
- enabling the Mozilla plugin in OpenOffice.org and opening a
.odt
file in Firefox would generate a segmentation fault, causing Firefox to crash on x86_64 architectures. A patch has been applied to define theuint32
andint32
variables as the appropriate type of int or long depending on the architecture. (BZ#496033) - when performing an Edit → Find & Replace operation in OpenOffice.org Impress, the Find All button was visible but inactive. A patch has been applied to remove the Find All button from the interface as this is not a supported OpenOffice.org Impress feature. (BZ#504109)
- when attempting to merge a
.sxi
or.odt
file into an OpenOffice.org Calc document, the application would crash due to theSfxMedium* pMed
pointer inScDocShell::DialogClosedHdl()
being set toNULL
. A patch has been applied to thedocsh4.cxx
file to test the state of this variable prior to affecting the merge. (BZ#504551) - when using OpenOffice.org Calc with spell check enabled, if a misspelt word was entered in a cell and the Edit → Repeat:Insert operation was attempted from within a new cell, the misspelt word will would not be inserted. The
viewfunc.cxx
file has been updated to ensure that the insert operation is functional even if the original cell contents are misspelt. (BZ#504967) - in OpenOffice.org Calc, the Data → Group and Outline → AutoOutline command would not work for any cell that contained a formula specifying a cell range as a list (for example: =SUM(A1;A2;A3)). To fix this bug the
cell.hxx
file has been modified to simplify a list range (for example: the list A2;A1;A3 would become A1:A3). By condensing the list, the Data → Group and Outline → AutoOutline command now works as expected. (BZ#504971) - building
RPM
s for OpenOffice.org would fail when a Java version above version 1.4 was installed. This occurred because the ANT scripts used to build some of the components were not configured to generate version 1.4 compatible bytecode upon which OpenOffice.org is dependent. This bug has since been fixed by enforcingRPM
s to be built with the GNU Compiler for Java (GCJ) or the Eclipse Compiler for Java (EJC). GJC specific options have been omitted as these are not recognized by EJC. This ensures that OpenOffice.orgRPM
s are generated without error when using therpmbuild
command. (BZ#506036) - when printing, OpenOffice.org would sometimes crash. This was due to the code that processes Postscript Printer Description (PPD) keys from CUPS inserting a value of
None
as the first value for each newly inserted key. Under these circumstances the second insertion returns aNULL
pointer and the following statement causes the crash by dereferencing the pointer. To correct this bug thejobset.cxx
file has been modified to only insert a value ofNone
as the first value for each newly inserted key if it is not already present. (BZ#515488) - when zooming in over 128% on a document in the OpenOffice.org Writer, any inserted note would no longer be viewable. By upgrading the OpenOffice.org suite to 3.1.1-19.5 this issue is no longer presented. (BZ#521006)
- bulleted lists in an OpenOffice.org Writer version 3 document would not render when opened in OpenOffice.org Writer version 2.3.0. By upgrading the OpenOffice.org suite to 3.1.1-19.5 this issue is no longer presented. (BZ#527933)
- the OpenOffice.org Calc application would crash when custom colors were created. These updated packages fix an improperly declared variable that caused the bug. Custom colors can now be created successfully. (BZ#530355)
- the OpenOffice.org package prior to version 3.1.1 did not support Microsoft 2007 Office
Open XML
(OOXML) file formats resulting in the inability to open files of this type. The OpenOffice.org 3.1.1-19.5 suite provides the necessary support to open OOXML file formats includingpptx
,xlsx
anddocx
. (BZ#444052)
1.144. openssh
1.144.1. RHBA-2009:1668: bug fix update
Note
1.144.2. RHBA-2010:0123: bug fix update
Note
1.144.3. RHSA-2009:1470: Moderate security update
Important
1.144.4. RHBA-2010:0193: bug fix update
1.145. openssl
1.145.1. RHSA-2010:0162: Important security update
Important
1.145.2. RHSA-2010:0054: Moderate security update
Important
1.146. openswan
1.146.1. RHBA-2010:0096: bug fix update
Note
1.146.2. RHBA-2009:1612: bug fix update
Note
1.147. oprofile
1.147.1. RHBA-2010:0283: bug fix and enhancement update
1.148. pam
1.148.1. RHBA-2010:0135: bug fix update
Note
1.149. pam_krb5
1.149.1. RHSA-2010:0258: Low security and bug fix update
1.150. paps
1.150.1. RHBA-2009:1679: bug fix update
Note
1.151. parted
1.151.1. RHBA-2010:0257: bug fix update
1.152. pax
1.152.1. RHBA-2009:1591: bug fix update
Note
1.153. pciutils
1.153.1. RHBA-2009:1592: bug fix update
Note
1.154. pcsc-lite
1.154.1. RHBA-2010:0278: bug fix update
1.155. perl-Sys-Virt
1.155.1. RHBA-2010:0251: bug fix update
1.156. perl-XML-SAX
1.156.1. RHBA-2010:0008: and perl-XML-LibXML bug fix update
Note
1.157. pexpect
1.157.1. RHBA-2009:1508: bug fix update
Note
1.158. php
1.158.1. RHSA-2010:0040: Moderate security update
Important
1.158.2. RHBA-2010:0241: bug fix and enhancement update
1.159. pidgin
1.159.1. RHBA-2010:0176: bug fix update
Note
1.160. piranha
1.160.1. RHBA-2010:0297: bug fix update
1.161. pirut
1.161.1. RHBA-2010:0058: bug fix update
Note
1.162. policycoreutils
1.162.1. RHBA-2010:0208: bug fix update
1.163. poppler
1.163.1. RHSA-2009:1504: Important security and bug fix update
Important
1.164. postgresql
1.164.1. RHSA-2009:1484: Moderate security update
Important
1.165. ppc64-utils
1.165.1. RHBA-2010:0225: bug fix and enhancement update
1.166. procps
1.166.1. RHBA-2010:0200: bug fix and enhancement update
1.167. pykickstart
1.167.1. RHBA-2010:0248: bug fix and enhancement update
1.168. python-virtinst
1.168.1. RHBA-2010:0282: bug fix and enhancement update
1.169. PyXML
1.169.1. RHSA-2010:0002: Moderate security update
Important
1.170. qspice
1.170.1. RHBA-2009:1489: bug fix update
Note