linux-kernel - how to read block device size from sysfs?

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: <201012011729.18661.lists@egidy.de>
Date:	Wed, 1 Dec 2010 17:29:18 +0100
From:	"Gerd v. Egidy" <lists@...dy.de>
To:	linux-kernel@...r.kernel.org
Subject: how to read block device size from sysfs?

Hi,

I want to read the size of a block device in bytes from sysfs.

There are /sys/block/<device>/size and 
/sys/block/<device>/<device><partition>/size.

But these values are reported in sectors, not in bytes. As discs with 4K 
sectors are on the horizon now, I don't want to make wrong assumptions on the 
sector size.

So what is the correct sector size for /sys/block/<device>/size?

/sys/block/<device>/queue/logical_block_size,
/sys/block/<device>/queue/physical_block_size or something else?

While searching for an answer I've stumbled across some reports about drives 
lying about their sector sizes to "improve" compatibility. Is there some best 
practice to still get the correct size in bytes?

Kind regards,

Gerd

-- 
Address (better: trap) for people I really don't want to get mail from:
jonas@...tusamerica.com
--
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/