| 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
| ||
|
Message-Id: <1186468623.2700.4.camel@laptopd505.fenrus.org> Date: Mon, 06 Aug 2007 23:37:03 -0700 From: Arjan van de Ven <arjan@...radead.org> To: Neil Brown <neilb@...e.de> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH/RFC] allow mapping from block-device-file to sysfs entry. On Tue, 2007-08-07 at 16:07 +1000, Neil Brown wrote: > Suppose that in a program I have an open file descriptor for a device, > and I want to find the /sys/block information for this device. > There is currently no direct way to do this. I need to read > /sys/block/*/dev, /sys/block/*/*/dev > and match major/minor numbers with the result from fstat. > > I would like a more direct mechanism. > > The following patch is a proposal for such a mechanism. > > It provides an 'ioctl' which returns then 'name' of the device, as > generated by bdevname. This is the same name that is used to create > entries in sysfs. > For a partition of a device, it returns 'device/partition'. how about returning the entire path relative to the start of sysfs? That way, if things move or something you're tolerant against that.... (I'd not be against making this a generic IOCTL for every device, a SYSFSLOCATION kind of ioctl... it's by no means block specific...) - 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/
Powered by blists - more mailing lists