netdev - Re: [ofa-general] Re: [PATCH v3 08/13] QLogic VNIC: sysfs interface implementation for the driver

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <adazlpzzvjn.fsf@cisco.com>
Date:	Thu, 05 Jun 2008 09:38:36 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	Dave Dillow <dillowda@...l.gov>
Cc:	Amar Mudrankit <amar.mudrankit@...gic.com>,
	Greg KH <greg@...ah.com>, netdev@...r.kernel.org,
	Stephen Hemminger <shemminger@...tta.com>,
	general@...ts.openfabrics.org, poornima.kamath@...gic.com
Subject: Re: [ofa-general] Re: [PATCH v3 08/13] QLogic VNIC: sysfs interface implementation for the driver

 > That said, given that SRP's been using sysfs since it went in, is there
 > a reason to move to configfs other than it's the new preferred way to do
 > it? Given the desire to not break ABI's -- and IIRC sysfs was declared to
 > be under that unbrella -- wouldn't we have to at least carry both
 > interfaces for a while, assuming we can even get rid of the sysfs one?

Yes, we'd definitely be carrying both interfaces for at least a year.

Looking further into this, I'm not sure it makes much sense either.
Another problem with configfs is that the lifetime of the object is
controlled by userspace.  So if we lose a connection to a target,
the object will persist in configfs until userspace notices.

 - R.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html