From: David Miller <davem@davemloft.net>
To: dingtianhong@huawei.com
Cc: kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
kaber@trash.net, netdev@vger.kernel.org
Subject: Re: [PATCH net v2] igmp: fix the problem when mc leave group
Date: Mon, 07 Jul 2014 21:31:32 -0700 (PDT) [thread overview]
Message-ID: <20140707.213132.448071496887411114.davem@davemloft.net> (raw)
In-Reply-To: <53B39DB8.2060306@huawei.com>
From: Ding Tianhong <dingtianhong@huawei.com>
Date: Wed, 2 Jul 2014 13:50:48 +0800
> The problem was triggered by these steps:
>
> 1) create socket, bind and then setsockopt for add mc group.
> mreq.imr_multiaddr.s_addr = inet_addr("255.0.0.37");
> mreq.imr_interface.s_addr = inet_addr("192.168.1.2");
> setsockopt(sockfd, IPPROTO_IP, IP_ADD_MEMBERSHIP, &mreq, sizeof(mreq));
>
> 2) drop the mc group for this socket.
> mreq.imr_multiaddr.s_addr = inet_addr("255.0.0.37");
> mreq.imr_interface.s_addr = inet_addr("0.0.0.0");
> setsockopt(sockfd, IPPROTO_IP, IP_DROP_MEMBERSHIP, &mreq, sizeof(mreq));
>
> 3) and then drop the socket, I found the mc group was still used by the dev:
>
> netstat -g
>
> Interface RefCnt Group
> --------------- ------ ---------------------
> eth2 1 255.0.0.37
>
> Normally even though the IP_DROP_MEMBERSHIP return error, the mc group still need
> to be released for the netdev when drop the socket, but this process was broken when
> route default is NULL, the reason is that:
>
> The ip_mc_leave_group() will choose the in_dev by the imr_interface.s_addr, if input addr
> is NULL, the default route dev will be chosen, then the ifindex is got from the dev,
> then polling the inet->mc_list and return -ENODEV, but if the default route dev is NULL,
> the in_dev and ifIndex is both NULL, when polling the inet->mc_list, the mc group will be
> released from the mc_list, but the dev didn't dec the refcnt for this mc group, so
> when dropping the socket, the mc_list is NULL and the dev still keep this group.
>
> v1->v2: According Hideaki's suggestion, we should align with IPv6 (RFC3493) and BSDs,
> so I add the checking for the in_dev before polling the mc_list, make sure when
> we remove the mc group, dec the refcnt to the real dev which was using the mc address.
> The problem would never happened again.
>
> Signed-off-by: Ding Tianhong <dingtianhong@huawei.com>
Applied, thank you.
next prev parent reply other threads:[~2014-07-08 4:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 5:50 [PATCH net v2] igmp: fix the problem when mc leave group Ding Tianhong
2014-07-08 4:31 ` David Miller [this message]
2014-07-08 4:47 ` Ding Tianhong
2014-07-08 4:59 ` David 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=20140707.213132.448071496887411114.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dingtianhong@huawei.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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 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).