linux-kernel - Re: How to map ata_link to physical link and ata

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 17 Jul 2012 09:59:35 +0800
From:	Yang Bai <hamo.by@...il.com>
To:	jgarzik@...ox.com, gwendal@...gle.com, jgarzik@...hat.com
Cc:	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: How to map ata_link to physical link and ata_port to physical port

CC-ed Gwendal and Jeff

Ping.

On Mon, Jul 16, 2012 at 11:09 AM, Yang Bai <hamo.by@...il.com> wrote:
> Hi hackers,
>
> In our internal usage, we want to map the disk in system like
> sd{a,b,c} to physical disk slot. When the disk is attached to LSI HBA
> card, we find that we can rely on the phy attribute of the disk to
> find the slot since this attribute does not change no matter which
> kind of disks we attach or what order we attach the disks. But when
> doing this for AHCI, we do not find an attribute that we can rely on
> it to map the disk to slot. No matter ata_port number or ata_host
> number, when we changed the order we attached the disks to slots, they
> changed.
>
> So I want to know is there some attribute we can get from AHCI that
> map the logical disk to physical slot?
>
> Thanks,
> Yang



-- 
    """
    Keep It Simple,Stupid.
    """

Chinese Name: 白杨
Nick Name: Hamo
Homepage: http://hamobai.com/
GPG KEY ID: 0xA4691A33
Key fingerprint = 09D5 2D78 8E2B 0995 CF8E  4331 33C4 3D24 A469 1A33
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/