• Peter Oberparleiter's avatar
    dasd: use correct label location for diag fba disks · a4693e59
    Peter Oberparleiter authored
    commit cffab6bc upstream.
    
    Partition boundary calculation fails for DASD FBA disks under the
    following conditions:
    - disk is formatted with CMS FORMAT with a blocksize of more than
      512 bytes
    - all of the disk is reserved to a single CMS file using CMS RESERVE
    - the disk is accessed using the DIAG mode of the DASD driver
    
    Under these circumstances, the partition detection code tries to
    read the CMS label block containing partition-relevant information
    from logical block offset 1, while it is in fact located at physical
    block offset 1.
    
    Fix this problem by using the correct CMS label block location
    depending on the device type as determined by the DASD SENSE ID
    information.
    Signed-off-by: default avatarPeter Oberparleiter <peter.oberparleiter@de.ibm.com>
    Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
    [bwh: Adjust for 2.6.32]
    Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
    a4693e59
ibm.c 6.5 KB