From: Takashi Hibi <hibi665@oki.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: netdev@oss.sgi.com, davem@redhat.com
Subject: Re: MLD problems (again) [PATCH]
Date: Tue, 13 Jan 2004 16:59:41 +0900 [thread overview]
Message-ID: <20040113165941.730c0345%hibi665@oki.com> (raw)
In-Reply-To: (Your message of "Tue, 13 Jan 2004 14:40:59 +0900") <20040113144059.728d0998%hibi665@oki.com>
David,
Good news.
I found a mistake which I made when I built the kernel.
After fixing it, the problem is solved and the Linux box can join
multicast group at once.
The patch is OK.
Thank you.
Takashi Hibi
> David,
>
> The patch is very simple and I have no problem to apply it to 2.4 line kernel.
> I already applied this patch, but it didn't solve the problem.
>
> Regards,
> Takashi Hibi
>
>>
>>
>>
>>
>> Takashi,
>> The patch I sent was for 2.6.1, but it should also apply to
>> 2.4 line kernels and fix the problem. If you have problems getting
>> it to apply in 2.4, let me know what version and I can provide you
>> a patch specific for that kernel.
>>
>> +-DLS
>>
>>
>> Takashi Hibi <hibi665@oki.com> on 01/12/2004 03:04:48 AM
>>
>> To: David Stevens/Beaverton/IBM@IBMUS
>> cc: netdev@oss.sgi.com, davem@redhat.com
>> Subject: Re: MLD problems (again) [PATCH]
>>
>>
>>
>> David,
>>
>> Thank you for the patch.
>> But at least it doesn't solve the problem for 2.4 line kernel.
>> I will also test with 2.6.1 later.
>>
>> Regards,
>> Takashi Hibi
>>
>>>
>>>
>>>
>>>
>>> Takashi,
>>> I believe the patch below will fix the problem you
>>> had with MCAST_JOIN_SOURCE_GROUP not sending a
>>> report. There was a typo in the source filter switching that did
>>> two deletes, rather than an delete and an add.
>>>
>>> Dave,
>>> Although IGMPv3 didn't have any problems, this patch
>>> also re-arranges the order of the filter changes. I think it's cleaner
>>> to add the new one first and then delete the old one, rather than
>>> having a small window with no filter set. So, this is a bug fix for MLD
>>> and a code clean-up for IGMPv3.
>>> This bug and patch should also apply to the 2.4 line.
>>>
>>> +-DLS
>>>
>>> [included in-line for viewing and as an attachment for unmangled
>>> whitespace]
>>>
>>> --- linux-2.6.1/net/ipv6/mcast.c 2004-01-08 22:59:56.000000000 -0800
>>> +++ linux-2.6.1F1/net/ipv6/mcast.c 2004-01-11 21:06:05.000000000 -0800
>>> @@ -372,9 +372,9 @@
>>> goto done;
>>> } else if (pmc->sfmode != omode) {
>>> /* allow mode switches for empty-set filters */
>>> + ip6_mc_add_src(idev, group, omode, 0, 0, 0);
>>> ip6_mc_del_src(idev, group, pmc->sfmode, 0, 0, 0);
>>> pmc->sfmode = omode;
>>> - ip6_mc_del_src(idev, group, pmc->sfmode, 0, 0, 0);
>>> }
>>>
>>> psl = pmc->sflist;
>>> --- linux-2.6.1/net/ipv4/igmp.c 2004-01-08 23:00:12.000000000 -0800
>>> +++ linux-2.6.1F1/net/ipv4/igmp.c 2004-01-11 21:27:41.000000000 -0800
>>> @@ -1749,11 +1749,10 @@
>>> goto done;
>>> } else if (pmc->sfmode != omode) {
>>> /* allow mode switches for empty-set filters */
>>> + ip_mc_add_src(in_dev, &mreqs->imr_multiaddr, omode, 0, 0, 0);
>>> ip_mc_del_src(in_dev, &mreqs->imr_multiaddr, pmc->sfmode, 0,
>>> 0, 0);
>>> pmc->sfmode = omode;
>>> - ip_mc_add_src(in_dev, &mreqs->imr_multiaddr, pmc->sfmode, 0,
>>> - 0, 0);
>>> }
>>>
>>> psl = pmc->sflist;
>>>
>>> (See attached file: 2.6.1MLD.patch)
>>
>>
next prev parent reply other threads:[~2004-01-13 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 18:54 MLD problems (again) [PATCH] David Stevens
2004-01-13 5:40 ` Takashi Hibi
2004-01-13 7:59 ` Takashi Hibi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-13 8:07 David Stevens
2004-01-12 5:49 David Stevens
2004-01-12 11:04 ` Takashi Hibi
2004-01-14 0:15 ` David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040113165941.730c0345%hibi665@oki.com \
--to=hibi665@oki.com \
--cc=davem@redhat.com \
--cc=dlstevens@us.ibm.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).