- Issued:
- 2011-07-21
- Updated:
- 2011-07-21
RHBA-2011:0981 - Bug Fix Advisory
Synopsis
device-mapper bug fix and enhancement update
Type/Severity
Bug Fix Advisory
Red Hat Insights patch analysis
Identify and remediate systems affected by this advisory.
Topic
Updated device-mapper packages that fix several bugs and add various
enhancements are now available for Red Hat Enterprise Linux 5.
Description
The device-mapper packages provide a library required by logical volume
management utilities such as LVM2 and dmraid.
The device-mapper package has been upgraded to upstream version 1.02.63, which
provides a number of bug fixes and enhancements over the previous version.
(BZ#680958) Those enhancements include:
- Unlink failure in the remove_lockfile() function in dmeventd is now checked
for.
- Inactive table query support is now supported when using the Red Hat
Enterprise Linux 5.7 kernel. The "dmsetup table --inactive" command can be run
to view the contents of the inactive table instead of the live one, which is the
default.
- The dm_task_secure_data() function has been added to libdevmapper to wipe the
ioctl buffers in the kernel.
- A new "-R" option has been added to restart dmeventd without loss of state.
These updated device-mapper packages provide fixes for the following bugs:
- Previously, booting encrypted devices which used Multi-Level Security (MLS)
enforcing mode failed with this error message:
/dev/mapper/temporary-cryptsetup-977: lsetfilecon failed: Operation not
permitted
The problem occurred when cryptsetup created a device node and relabeled it
using the lsetfilecon() function instead of using the setfscreatecon() function.
This has been fixed and devices which used MLS enforcing mode now boot
successfully. (BZ#584884)
- When installing the kernel-2.6.18 packages, this error message was logged to
the /root/install.log file: "matchpathcon failed: No such file or directory".
The problem has been fixed and this error message is no longer logged to
install.log with this update. (BZ#695374)
- This update fixes a conflict which occurred when lvm2 and the device mapper
debuginfo packages were installed together. (BZ#701715)
Users are advised to upgrade to these updated device-mapper packages, which
resolve these bugs and add these enhancements.
Solution
Before applying this update, make sure that all previously-released errata
relevant to your system have been applied.
This update is available via Red Hat Network. Details on how to use the Red Hat
Network to apply this update are available at
https://access.redhat.com/kb/docs/DOC-11259
Affected Products
- Red Hat Enterprise Linux Server 5 x86_64
- Red Hat Enterprise Linux Server 5 ia64
- Red Hat Enterprise Linux Server 5 i386
- Red Hat Enterprise Linux Workstation 5 x86_64
- Red Hat Enterprise Linux Workstation 5 i386
- Red Hat Enterprise Linux Desktop 5 x86_64
- Red Hat Enterprise Linux Desktop 5 i386
- Red Hat Enterprise Linux for IBM z Systems 5 s390x
- Red Hat Enterprise Linux for Power, big endian 5 ppc
- Red Hat Enterprise Linux Server from RHUI 5 x86_64
- Red Hat Enterprise Linux Server from RHUI 5 i386
Fixes
- BZ - 584884 - Device node creation code should use setfscreatecon()
- BZ - 680958 - Upgrade device-mapper to 1.02.63 version
- BZ - 695374 - matchpathcon failed: No such file or directory
- BZ - 701715 - file /usr/src/debug/LVM2.2.02.84/daemons/dmeventd/libdevmapper-event.c from install of lvm2-debuginfo-2.02.84-3.el5.x86_64 conflicts with file from package device-mapper-debuginfo-1.02.63-2.el5.x86_64
CVEs
(none)
References
(none)
Red Hat Enterprise Linux Server 5
SRPM | |
---|---|
device-mapper-1.02.63-4.el5.src.rpm | SHA-256: 104e80eb9edd3bcaf9ea34f4f88a6bfe799c9a129a5a5b9db4e19fc2cd1c7fde |
x86_64 | |
device-mapper-1.02.63-4.el5.i386.rpm | SHA-256: e7fb1bce3e9c24df6a8e8869205bc36185481e40ab6e0d58a917636ae276019c |
device-mapper-1.02.63-4.el5.x86_64.rpm | SHA-256: 8acd74b40ed71b55c7f8828f9a70353a2f88f6a96d8fca83e677747787974456 |
device-mapper-event-1.02.63-4.el5.x86_64.rpm | SHA-256: 31996c536f2d6dd01ac0e80516a7ed2f79bb019e2facc713dbd070794e855ec3 |
ia64 | |
device-mapper-1.02.63-4.el5.i386.rpm | SHA-256: e7fb1bce3e9c24df6a8e8869205bc36185481e40ab6e0d58a917636ae276019c |
device-mapper-1.02.63-4.el5.ia64.rpm | SHA-256: 64ae7e171a44174c72cae9e5bd1d953087c83b890d5e0d10e494bf38dde5c0a1 |
device-mapper-event-1.02.63-4.el5.ia64.rpm | SHA-256: c589c996a0d2493057141f459326724d2f258f07a3400fdfe96fb9b0cf55db8a |
i386 | |
device-mapper-1.02.63-4.el5.i386.rpm | SHA-256: e7fb1bce3e9c24df6a8e8869205bc36185481e40ab6e0d58a917636ae276019c |
device-mapper-event-1.02.63-4.el5.i386.rpm | SHA-256: e98c3f98993d0bec0ab0521d3edc885ea74258378997e59e37719aa21f9a0eec |
Red Hat Enterprise Linux Workstation 5
SRPM | |
---|---|
device-mapper-1.02.63-4.el5.src.rpm | SHA-256: 104e80eb9edd3bcaf9ea34f4f88a6bfe799c9a129a5a5b9db4e19fc2cd1c7fde |
x86_64 | |
device-mapper-1.02.63-4.el5.i386.rpm | SHA-256: e7fb1bce3e9c24df6a8e8869205bc36185481e40ab6e0d58a917636ae276019c |
device-mapper-1.02.63-4.el5.x86_64.rpm | SHA-256: 8acd74b40ed71b55c7f8828f9a70353a2f88f6a96d8fca83e677747787974456 |
device-mapper-event-1.02.63-4.el5.x86_64.rpm | SHA-256: 31996c536f2d6dd01ac0e80516a7ed2f79bb019e2facc713dbd070794e855ec3 |
i386 | |
device-mapper-1.02.63-4.el5.i386.rpm | SHA-256: e7fb1bce3e9c24df6a8e8869205bc36185481e40ab6e0d58a917636ae276019c |
device-mapper-event-1.02.63-4.el5.i386.rpm | SHA-256: e98c3f98993d0bec0ab0521d3edc885ea74258378997e59e37719aa21f9a0eec |
Red Hat Enterprise Linux Desktop 5
SRPM | |
---|---|
device-mapper-1.02.63-4.el5.src.rpm | SHA-256: 104e80eb9edd3bcaf9ea34f4f88a6bfe799c9a129a5a5b9db4e19fc2cd1c7fde |
x86_64 | |
device-mapper-1.02.63-4.el5.i386.rpm | SHA-256: e7fb1bce3e9c24df6a8e8869205bc36185481e40ab6e0d58a917636ae276019c |
device-mapper-1.02.63-4.el5.x86_64.rpm | SHA-256: 8acd74b40ed71b55c7f8828f9a70353a2f88f6a96d8fca83e677747787974456 |
device-mapper-event-1.02.63-4.el5.x86_64.rpm | SHA-256: 31996c536f2d6dd01ac0e80516a7ed2f79bb019e2facc713dbd070794e855ec3 |
i386 | |
device-mapper-1.02.63-4.el5.i386.rpm | SHA-256: e7fb1bce3e9c24df6a8e8869205bc36185481e40ab6e0d58a917636ae276019c |
device-mapper-event-1.02.63-4.el5.i386.rpm | SHA-256: e98c3f98993d0bec0ab0521d3edc885ea74258378997e59e37719aa21f9a0eec |
Red Hat Enterprise Linux for IBM z Systems 5
SRPM | |
---|---|
device-mapper-1.02.63-4.el5.src.rpm | SHA-256: 104e80eb9edd3bcaf9ea34f4f88a6bfe799c9a129a5a5b9db4e19fc2cd1c7fde |
s390x | |
device-mapper-1.02.63-4.el5.s390.rpm | SHA-256: 041a1f7433cc29eda9808aa890e61287d9533da7206168b65e82db180ab70d86 |
device-mapper-1.02.63-4.el5.s390x.rpm | SHA-256: 02d1e6c801fdea9542fca2ac6e5255a20485ab9365054fcf697b8b1ac8c14fb4 |
device-mapper-event-1.02.63-4.el5.s390x.rpm | SHA-256: 9b24bac39bcb1937248356d91bbc489f4027d8ecff304b591f7781456322d19d |
Red Hat Enterprise Linux for Power, big endian 5
SRPM | |
---|---|
device-mapper-1.02.63-4.el5.src.rpm | SHA-256: 104e80eb9edd3bcaf9ea34f4f88a6bfe799c9a129a5a5b9db4e19fc2cd1c7fde |
ppc | |
device-mapper-1.02.63-4.el5.ppc.rpm | SHA-256: 27c09c2dfad556366bbbd8ee3fae83c00a93accd85b1955e50078410a51eac14 |
device-mapper-1.02.63-4.el5.ppc64.rpm | SHA-256: 000fd1f776aaa2d237d2c50fcd5d7cd3e31a508c3f0b846d33d4365c6dd1748b |
device-mapper-event-1.02.63-4.el5.ppc.rpm | SHA-256: 8226bfc3351d98553ad1cdd4516cd9b449b08801692fd5ee788cc5b235eef7b7 |
Red Hat Enterprise Linux Server from RHUI 5
SRPM | |
---|---|
device-mapper-1.02.63-4.el5.src.rpm | SHA-256: 104e80eb9edd3bcaf9ea34f4f88a6bfe799c9a129a5a5b9db4e19fc2cd1c7fde |
x86_64 | |
device-mapper-1.02.63-4.el5.i386.rpm | SHA-256: e7fb1bce3e9c24df6a8e8869205bc36185481e40ab6e0d58a917636ae276019c |
device-mapper-1.02.63-4.el5.x86_64.rpm | SHA-256: 8acd74b40ed71b55c7f8828f9a70353a2f88f6a96d8fca83e677747787974456 |
device-mapper-event-1.02.63-4.el5.x86_64.rpm | SHA-256: 31996c536f2d6dd01ac0e80516a7ed2f79bb019e2facc713dbd070794e855ec3 |
i386 | |
device-mapper-1.02.63-4.el5.i386.rpm | SHA-256: e7fb1bce3e9c24df6a8e8869205bc36185481e40ab6e0d58a917636ae276019c |
device-mapper-event-1.02.63-4.el5.i386.rpm | SHA-256: e98c3f98993d0bec0ab0521d3edc885ea74258378997e59e37719aa21f9a0eec |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.