From: Patrick McHardy <kaber@trash.net>
To: Reither Robert <Robert.Reither@av-digital.at>
Cc: David Stevens <dlstevens@us.ibm.com>, netdev@vger.kernel.org
Subject: Re: AW: AW: Problem receiving multicast with kernel.2.6.24 #3
Date: Tue, 19 Feb 2008 15:02:33 +0100 [thread overview]
Message-ID: <47BAE179.9030103@trash.net> (raw)
In-Reply-To: <BA41E8A07B73A041948C2E3A4EF6239D062F1A@av-digital-exch.avdigital.at>
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
Reither Robert wrote:
> Visit AVD on prolight+sound in Frankfurt from 12.-15. March 2008 - Hall 8.0, Stand G16
> ________________________________________________________________________
>
>
>
> OK, found one solution (but i think, this should not the normal way)
>
> MC joining first the VLAN device (eth0.3) and than the physical (eth0) does the trick, 100% success ...
>
> Doing it the opposite way, gives the same problem as before ...
>
> So somehow joining the VLAN interface disrupts the join to the physical one ...
>
> Ideas ?
Does this patch help?
[-- Attachment #2: x --]
[-- Type: text/plain, Size: 1058 bytes --]
commit 6548b91f39381b2c5f02f99c14734546354bff89
Author: Jorge Boncompte [DTI2] <jorge@dti2.net>
Date: Mon Feb 18 16:02:01 2008 +0100
[NET]: Messed multicast lists after dev_mc_sync/unsync
Commit a0a400d79e3dd7843e7e81baa3ef2957bdc292d0 from you
introduced a new field "da_synced" to struct dev_addr_list that is
not properly initialized to 0. So when any of the current users (8021q,
macvlan, mac80211) calls dev_mc_sync/unsync they mess the address
list for both devices.
The attached patch fixed it for me and avoid future problems.
Signed-off-by: Jorge Boncompte [DTI2] <jorge@dti2.net>
Signed-off-by: Patrick McHardy <kaber@trash.net>
diff --git a/net/core/dev.c b/net/core/dev.c
index 6cfc123..9516105 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -2900,7 +2900,7 @@ int __dev_addr_add(struct dev_addr_list **list, int *count,
}
}
- da = kmalloc(sizeof(*da), GFP_ATOMIC);
+ da = kzalloc(sizeof(*da), GFP_ATOMIC);
if (da == NULL)
return -ENOMEM;
memcpy(da->da_addr, addr, alen);
prev parent reply other threads:[~2008-02-19 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 13:57 AW: AW: Problem receiving multicast with kernel.2.6.24 #3 Reither Robert
2008-02-19 14:02 ` Patrick McHardy [this message]
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=47BAE179.9030103@trash.net \
--to=kaber@trash.net \
--cc=Robert.Reither@av-digital.at \
--cc=dlstevens@us.ibm.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 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).