Hi, Based on TIPC release change log following are the list of TIPC multicast Bugs that are fixed for Linux kernels 2.6.22-2.6.27 and Higher
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ 1) prevent delivery/non-delivery of multicast messages to out-of-scope/in-scope destinations [http://sourceforge.net/p/tipc/bugs/75/] fixed in TIPC 1.7.6 A long-standing bug in the delivery of multicast messages, affecting TIPC 1.5.3 through 1.7.5 (and possibly affecting earlier versions), has been discovered. This bug may result in an incoming multicast message being incorrectly delivered to ports that published corresponding names with "node" scope, or in a multicast message not being correctly delivered to ports that published corresponding names with "cluster" or "zone" scope. Note: This bug will only cause problems if a TIPC node's name table contains publications for the same name (or name sequence) that use both "node" and "cluster"/"zone" scope. example: An application creates a socket that binds the name {X,Y} with "node" scope; a second application (possibly on a different node) creates another socket that binds the name {X,Y} with "cluster" scope. 2) optimization to multicast name lookup algorithm [http://sourceforge.net/p/tipc/bugs/76/] fixed in TIPC 1.7.6 TIPC's algorithm for identifying on-node and off-node destinations that overlap a multicast name sequence range is not as efficient as it could be. Rather than traversing the list of all known name publications within the cluster, it should just traverse the (potentially much shorter) list of name publications made by the node itself, and determine if any off-node destinations exist by comparing the sizes of the two lists. (Since the node list must be a subset of the cluster list, a difference in sizes means that at least one off-node destination must exist.) 3) renamed "multicast-link" to "broadcast-link" fixed in TIPC 1.7.4 4) eliminated slight risk of incorrect routing of an incoming bundled multicast message fixed in TIPC 1.7.3 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ -AVM On 10/8/2014 4:05 PM, Anders Widell wrote: > Hi! > > OpenSAF 4.5 doesn't require any new features present in Linux kernel > versions beyond 2.6.32. However, there are bugs in TIPC multicast that > affect OpenSAF 4.5, and these bugs are known to have been fixed in Linux > kernel version 3.16. Bug-fixes are often back-ported to older versions > of the kernel that are still being maintained, but I don't know which > versions (if any) that contain these bug-fixes. You may be able to get > Linux kernel support from your Linux distribution vendor, to ensure that > your kernel has the relevant fixes. > > I agree that it would be convenient to be able to turn off usage of TIPC > multicast in OpenSAF, for cases where the kernel doesn't contain the > needed fixes. TIPC multicast is being used for improved performance, so > you wouldn't lose any functionality by turning it off. There have been > patches floating around for doing this, but a configuration option would > have been better. We will consider adding such a configuration option. > > regards, > Anders Widell > > On 10/07/2014 08:06 PM, Tony Hart wrote: >> If I understand correctly OSAF 4.5 requires kernel >= 3.16 when used with >> TIPC. That is going to be a show-stopper for many existing users. Can >> TIPC-multicast be disabled and if so does that allow 4.5 to be used on >> earlier kernels? >> >> thanks >> — >> tony >> >> On Oct 7, 2014, at 7:40 AM, Anders Widell <[email protected]> wrote: >> >>> Hello, >>> >>> The OpenSAF community is pleased to announce the General Availability of >>> the OpenSAF 4.5.0 enhancements release. The source code for OpenSAF 4.5.0 >>> and the corresponding documentation can be downloaded using the following >>> links: >>> >>> http://sourceforge.net/projects/opensaf/files/releases/opensaf-4.5.0.tar.gz/download >>> http://sourceforge.net/projects/opensaf/files/docs/opensaf-documentation-4.5.0.tar.gz/download >>> >>> For a complete list of new features in this release, please refer to the >>> NEWS at the wiki: >>> >>> https://sourceforge.net/p/opensaf/wiki/NEWS-4.5.0/ >>> >>> We have also released the maintenance (patch) releases OpenSAF 4.4.1 and >>> OpenSAF 4.3.3. >>> >>> - The source code for OpenSAF 4.4.1 and the corresponding documentation can >>> be downloaded using the following links: >>> >>> http://sourceforge.net/projects/opensaf/files/releases/opensaf-4.4.1.tar.gz/download >>> http://sourceforge.net/projects/opensaf/files/docs/opensaf-documentation-4.4.1.tar.gz/download >>> >>> See the ChangeLog for a full list of changes in this release: >>> >>> https://sourceforge.net/p/opensaf/wiki/ChangeLog-4.4.1/ >>> >>> - The source code for OpenSAF 4.3.3 and the corresponding documentation can >>> be downloaded using the following links: >>> >>> http://sourceforge.net/projects/opensaf/files/releases/opensaf-4.3.3.tar.gz/download >>> http://sourceforge.net/projects/opensaf/files/docs/opensaf-documentation-4.3.3.tar.gz/download >>> >>> See the ChangeLog for a full list of changes in this release: >>> >>> https://sourceforge.net/p/opensaf/wiki/ChangeLog-4.3.3/ >>> >>> Thank you for your continued interest in OpenSAF and to everyone who has >>> contributed to this release. >>> >>> regards, >>> Anders Widell >>> >>> >>> ------------------------------------------------------------------------------ >>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Opensaf-users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/opensaf-users >> > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Opensaf-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensaf-users ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
