[openib-general] [Bug 266] New: IPoIB multicast does not work with RHEL4 U4

[bugzilla-daemon at openib.org]

http://openib.org/bugzilla/show_bug.cgi?id=266

           Summary: IPoIB multicast does not work with RHEL4 U4
           Product: OpenFabrics Linux
           Version: 1.1rc6
          Platform: All
        OS/Version: RHEL 4
            Status: NEW
          Severity: major
          Priority: P2
         Component: IPoIB
        AssignedTo: bugzilla at openib.org
        ReportedBy: sweitzen at cisco.com


I'm opening a bug on this so customers can find this info more easily.

Email thread on issue:

On Tue, 2006-09-19 at 14:44 +0300, Eli cohen wrote:
> Hi,
> 
> while testing ipoib multicast on RHEL4.0 u4, I noticed that setsockopt()
> succeeds to add a multicast group to an interface but actually the
> multicast group is not added to the net_device. This means that an
> application cannot join a multicast group as a full member. When I
> examined the differences between the kernel sources for u3 and u4 I
> noticed that essential code was removed:
> 
> diff -ru net/ipv4/arp.c ../linux-2.6.9-42.ELsmp/net/ipv4/arp.c
> --- net/ipv4/arp.c  2006-09-18 15:35:03.000000000 +0300
> +++ ../linux-2.6.9-42.ELsmp/net/ipv4/arp.c  2006-09-19
> 10:08:06.000000000 +0300
> @@ -213,9 +213,6 @@
>     case ARPHRD_IEEE802_TR:
>         ip_tr_mc_map(addr, haddr);
>         return 0;
> -   case ARPHRD_INFINIBAND:
> -       ip_ib_mc_map(addr, haddr);
> -       return 0;
>     default:
>         if (dir) {
>             memcpy(haddr, dev->broadcast, dev->addr_len);
> 
> 
> Can anyone suggest a workaround to this issue?

Short of spinning a kernel, it's going to be hard to work around.
Thanks for finding this, I'll track down how this got left out of the U4
kernel when it was in the U3 kernel :-/

-- 
Doug Ledford <dledford at redhat.com>
              GPG KeyID: CFBFF194
              http://people.redhat.com/dledford

Infiniband specific RPMs available at
              http://people.redhat.com/dledford/Infiniband




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.