linux-kernel - Re: question about drivers/infiniband/core/cm.c's kobject usage

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:	Thu, 22 May 2008 14:58:12 -0700
From:	Greg KH <greg@...ah.com>
To:	Sean Hefty <sean.hefty@...el.com>
Cc:	rolandd@...co.com, hal.rosenstock@...il.com,
	general@...ts.openfabrics.org, linux-kernel@...r.kernel.org
Subject: Re: question about drivers/infiniband/core/cm.c's kobject usage

On Thu, May 22, 2008 at 02:47:51PM -0700, Sean Hefty wrote:
> >So I was curious, was this done on purpose?  If so, why?  If not, any
> >objection to me switching it over to be using struct device properly?
> 
> It's entirely possible I have this wrong, but the intent is to export some
> infiniband communication management message counters and relate them to the
> corresponding ib_device/port.  For example:
> 
> /sys/class/infiniband_cm/<device name>/<port number>/<counter group>/<counter>
> 
> (E.g. /sys/class/infiniband_cm/mthca0/1/cm_tx_msgs/req)
> 
> If there's a better way to handle this, I have no objection to changing it.

Yes, just hang all of the <port number> stuff off of the original
<device name> struct device.  That seems like it would be much simpler.

thanks,

greg k-h
--
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/