linux-kernel - Re: [PATCH 2/5] mtip32xx: Add new sysfs entry 'status' and fix restart port

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>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 6 Apr 2012 17:28:22 -0700
From:	Asai Thambi S P <asamymuthupa@...ron.com>
To:	Greg KH <greg@...ah.com>
CC:	Jens Axboe <axboe@...nel.dk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Sam Bradshaw <sbradshaw@...ron.com>
Subject: Re: [PATCH 2/5] mtip32xx: Add new sysfs entry 'status' and fix restart
 port

On 4/6/2012 4:30 PM, Greg KH wrote:

>>> > > What do the existing api files show for block devices?
>>> > > 
>> > 
>> > 
>> > I was looking into sysfs-driver-* files to create sysfs-driver-mtip32xx.
>> > These files have paths like /sys/bus/pci/*, /sys/devices/*,
>> > /sys/class/bluetooth/*, etc.
>> > 
>> > There are sysfs-block-dm and sysfs-block-zram files with
>> > /sys/block/dm-<num>/dm/* and /sys/block/zram<id>/*. If I have to follow
>> > these, then the file would be sysfs-driver-rssd with /sys/block/<disk>/*.
>> > 
>> > Let me know.
> /sys/block/rs*/ would be the right place, right?  You know the tree
> better than I do as you have this hardware and can see where in sysfs
> the files really are :)

Yes, I started that way and found /sys/block/rssda is a sym link to
/sys/devices/pci0000\:00/0000\:00\:01.0/0000\:01\:00.0/block/rssda/.
That is when I got the doubt, is it ok to use the sym link path or
should use the actual path.

I will go ahead with filename sysfs-block-rssd and path
/sys/block/rssd*/<entry>.

Thanks.

--
Regards,
Asai Thambi
--
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/