| 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: Thu, 29 Mar 2007 23:29:05 -0400 From: Bill Nottingham <notting@...hat.com> To: Greg KH <greg@...ah.com> Cc: Kay Sievers <kay.sievers@...y.org>, linux-kernel@...r.kernel.org Subject: Re: new sysfs layout and ethernet device names Greg KH (greg@...ah.com) said: > > If interfaces have to change, so be it. But changing the rules for > > using them years after it's implemented and then claiming "you didn't > > read the instructions" is pretty lame. > > That documentation has been in the kernel tree for almost a full year: It has a date on it. I'm not blind. That doesn't change the fact that that documentation: > Date: Thu Apr 27 14:10:12 2006 -0700 postdates the interface it's describing by at *least* two years. Which was the point of my mail that you conveniently ignored - retroactively deciding which parts of the interface you export to userspace shouldn't be used falls way short of best practices. > Anyway, yes, older code should still "just work" if you enable the > CONFIG_SYSFS_DEPRECATED config option in the kernel, that is what it is > there for. It appears to... the point was that (as far as the code is concerned) it's a silent break. Of course, code that expects the 'current' layout will then break when this new change is made, unless you add CONFIG_SYSFS_SLIGHTLY_LESS_DEPRECATED? Bill - 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