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
| ||
|
Message-ID: <20101020182411.GO8781@llucax.com.ar> Date: Wed, 20 Oct 2010 15:24:11 -0300 From: Leandro Lucarella <luca@...cax.com.ar> To: Jon Maloy <jon.maloy@...csson.com> Cc: Neil Horman <nhorman@...driver.com>, David Miller <davem@...emloft.net>, "paul.gortmaker@...driver.com" <paul.gortmaker@...driver.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "tipc-discussion@...ts.sourceforge.net" <tipc-discussion@...ts.sourceforge.net> Subject: Re: Linux 2.6.35/TIPC 2.0 ABI breaking changes Jon Maloy, el 20 de octubre a las 13:57 me escribiste: > > Another option is to change the TIPC 2.0 specification to use > > the old format (use HBO in subscriptions and keep > > TIPC_SUB_SERVICE as a separate flag with value 2) and forget > > about all this. After all, I can't see what advantages gives > > having to change the BO for internal messages between the > > applications and the stack. > > I agree with this. I have no problems with changing the draft > (which as Leandro already noted is "work-in-progress") to specify that > both HBO and NBO are permitted over the wire, and that it is the > topology server's task to keep track of which one is used. Just to try to understand better how things works, or are supposed to work: do the subscription and event messages (and I mean the struct tipc_subscr and tipc_event published in tipc.h) really go over the wire or are only used to communicate the stack to the application inside a node? I think this is a crucial matter, since it defines if the changes cross kernel/userspace boundaries only or it also crosses the kernel/network boundaries. > Remember, permitting both is a superset of the current one (NBO only) > so it is fully backwards compatible. We break absolutly nothing by > permitting this. I think if they really go through the wire, it should be in NBO, and if tipc_subscr and tipc_event are used only internally, we can still fix the userspace messages when sending them through the wire. In any case, I agree that the patches should be reverted and a solution should be planned with more time and consensus. Thanks. -- Leandro Lucarella (AKA luca) http://llucax.com.ar/ ---------------------------------------------------------------------- GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05) ---------------------------------------------------------------------- The world's best known word is "okay" The second most well-known word is "Coca-Cola" -- 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
Powered by blists - more mailing lists