| 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
| ||
|
Date: Fri, 17 Apr 2009 18:03:28 +0200 From: Kay Sievers <kay.sievers@...y.org> To: Daniel Debonzi <debonzi@...ux.vnet.ibm.com> Cc: Vladislav Bolkhovitin <vst@...b.net>, scst-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org Subject: Re: [Scst-devel] Discussion about SCST sysfs layout and implementation. On Fri, Apr 17, 2009 at 17:50, Daniel Debonzi <debonzi@...ux.vnet.ibm.com> wrote: > Do you mean that uses struct device is the right way to do it instead of > kobjects or it is just a option to get things on right places into sysfs? You can not put kobjects in /sys/devices/ and there will be no disconnected kobject tree just for scsi, unless the scsi maintainers really want want that, and then they should create their own filesystem instead, and not use kobjects at all. > I don't know this struct closely but my first impression looking to the > source code is that it is tied with hardware and has some complexity we > probably don't need. What do you think? If you want to integrate with the current scsi devices/objects, which is the only sensible option I think, you have to use struct device devices, kobjects will not get a classification in sysfs, and will be invisible for userspace tools unless you do random readdir() in /sys/devices/ to find them. Kay -- 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