All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dongpo Li <lidongpo@hisilicon.com>
To: netdev <netdev@vger.kernel.org>
Subject: question about function igmp_stop_timer() in net/ipv4/igmp.c
Date: Mon, 24 Oct 2016 19:50:12 +0800	[thread overview]
Message-ID: <580DF574.6070905@hisilicon.com> (raw)

Hello

We encountered a multicast problem when two set-top box(STB) join the same multicast group and leave.
The two boxes can join the same multicast group
but only one box can send the IGMP leave group message when leave,
the other box does not send the IGMP leave message.
Our boxes use the IGMP version 2.

I added some debug info and found the whole procedure is like this:
(1) Box A joins the multicast group 225.1.101.145 and send the IGMP v2 membership report(join group).
(2) Box B joins the same multicast group 225.1.101.145 and also send the IGMP v2 membership report(join group).
(3) Box A receives the IGMP membership report from Box B and kernel calls igmp_heard_report().
    This function will call igmp_stop_timer(im).
    In function igmp_stop_timer(im), it tries to delete IGMP timer and does the following:
        im->tm_running = 0;
        im->reporter = 0;
(4) Box A leaves the multicast group 225.1.101.145 and kernel calls
    ip_mc_leave_group -> ip_mc_dec_group -> igmp_group_dropped.
    But in function igmp_group_dropped(), the im->reporter is 0, so the kernel does not send the IGMP leave message.

I think there may be some problem in step (3).
The function igmp_stop_timer(im) should not set im->reporter to 0 if the IGMP timer has expired.
It should only work if the IGMP timer is running and does not send the IGMP join message.
I'm not sure whether it's a problem and hope any advice.

Thanks!


    Regards,
    Dongpo

.

             reply	other threads:[~2016-10-24 11:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 11:50 Dongpo Li [this message]
2016-10-24 15:32 ` question about function igmp_stop_timer() in net/ipv4/igmp.c Andrew Lunn
2016-10-25  1:13   ` Dongpo Li
2016-10-25  7:39     ` Andrew Lunn
2016-10-25 11:50       ` Dongpo Li
2016-10-25 12:19         ` Andrew Lunn

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=580DF574.6070905@hisilicon.com \
    --to=lidongpo@hisilicon.com \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.