Bug 679741

Summary: canonicalize swap devices
Product: Red Hat Enterprise Linux 6 Reporter: Karel Zak <kzak>
Component: util-linux-ngAssignee: Karel Zak <kzak>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: azelinka, jmarko, kvolny, rvokal
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 17:10:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Karel Zak 2011-02-23 11:51:54 UTC 
swapon(8) tries to activate already active swap partition if the swap area is on DM device. Fixed by upstream patch:

commit b98ff23e879826d0b041a18ca1090428748b9ef3
Author: Alexey Gladkov
Date:   Wed Dec 15 02:14:18 2010 +0300

    swapon: Canonicalize swap device
    
    Swapon checks whether a swap device is active by searching for the
    device name in /proc/swaps. /proc/swaps always specifies the path
    to real device file, even if the path to real device file, even
    if symlink was passed to the swapon() system call.
    
    This differs from /proc/mounts semantics where each string contains
    exactly the same device name as it was passed to the mount*() system call.
    
    If a swap partition resides on lvm, libblkid returns a name in
    form /dev/mapper/*, but now there are symlinks pointing to device
    files /dev/dm-*, resulting to /proc/swaps containing /dev/dm-*,
    but swapon still looks for /dev/mapper/* and tries to activate
    the swap partition again.
    
    [kzak: - remove unnecessary changes from
                        is_in_proc_swaps()]
    
    Signed-off-by: Alexey Gladkov
    Tested-by: Petr Uzel
    Signed-off-by: Karel
Comment 6 errata-xmlrpc 2011-12-06 17:10:39 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2011-1691.html