linux-kernel - get block_device from name

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <E1IxcpP-0002gv-Ng@elysium.home>
Date:	Wed, 28 Nov 2007 22:24:51 -0800
From:	Tim Barbour <trb@...sechangeit.com>
To:	linux-kernel@...r.kernel.org
Subject: get block_device from name

Please CC: me on any replies, as I am not subscribed to the list.

I want to do some bio IO on a block device (*no* filesystem involved).

First I need to get hold of the struct block_device. What is the current
recommended way to get from the name of a device (e.g. "/dev/sda1") to the
corresponding struct block_device ? What is the current canonical representation
of a device - dev_t ? Did kdev_t go away ?

Given the struct block_device, can I immediately use it in a bio, or do I need
to prepare the device first ?

I think I understand how to submit a bio, once I have the block_device ready.

I have read that the handling of block_devices is not as straightforward as it
could be... ( http://lwn.net/Articles/247072/ )

Any suggestions would be appreciated.

Again, please CC: me on any replies.

Tim
-
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/