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: Wed, 29 Aug 2007 13:12:32 -0500 From: Nathan Lynch <ntl@...ox.com> To: Joachim Fenkes <fenkes@...ibm.com> Cc: LinuxPPC-Dev <linuxppc-dev@...abs.org>, LKML <linux-kernel@...r.kernel.org>, Paul Mackerras <paulus@...ba.org>, Thomas Klein <tklein@...ibm.com>, Jan-Bernd Themann <themann@...ibm.com>, Christoph Raisch <raisch@...ibm.com>, Stefan Roscher <stefan.roscher@...ibm.com> Subject: Re: [PATCH 2.6.23] ibmebus: Prevent bus_id collisions Hi- Joachim Fenkes wrote: > Previously, ibmebus derived a device's bus_id from its location code. The > location code is not guaranteed to be unique, so we might get bus_id > collisions if two devices share the same location code. The OFDT full_name, > however, is unique, so we use that instead. This is a userspace-visible change, but I guess it's unavoidable. Will anything break? Also, I dislike this approach of duplicating the firmware device tree path in sysfs. Are GX/ibmebus devices guaranteed to be children of the same node in the OF device tree? If so, their unit addresses will be unique, and therefore suitable values for bus_id. I believe this is what the powerpc vio bus code does. - 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