From: "Bob Falken" <NetFestivalHaveFun@gmx.com>
To: "Hannes Frederic Sowa" <hannes@stressinduktion.org>,
"Julian Anastasov" <ja@ssi.bg>
Cc: netdev@vger.kernel.org
Subject: Re: Multicast routing stops functioning after 4G multicast packets recived.
Date: Tue, 07 Jan 2014 18:01:44 +0100 [thread overview]
Message-ID: <20140107170145.317040@gmx.com> (raw)
Hello,
I patched, kernel 3.2.53 yesterday,
8774002632packets, and ~9.1TB later, the multicast routing seems to function properly. :)
Kudos for fixing this.
I will keep checking the next days.
As for IPv6 MR, my current setup i.e: the Multicast source, does not support IPv6, so cannot do a check for that natively.
Unless I can translate IPv4 multicast into IPv6 multicast easily, using some iptable prerouting rules(?).
Thanks again.
----- Original Message -----
From: Hannes Frederic Sowa
Sent: 01/05/14 12:38 AM
To: Julian Anastasov
Subject: Re: Multicast routing stops functioning after 4G multicast packets recived.
On Sat, Jan 04, 2014 at 09:55:51PM +0200, Julian Anastasov wrote:
>
> Hello,
>
> On Thu, 19 Dec 2013, Bob Falken wrote:
>
> > Hello, I have an issue after kernel 2.6.37 and above.
> > If i roll back to kernel 2.6.36.4 everything is fine.
> > if recive more than 4294967295 multicast packets, the kernel does not register the multicast packets. and multicast routing does not functioning.
>
> ...
>
> > I think there might be a variable in the kernel that get overflown. though i cannot be sure as im not a programmer.
> >
> > Let me know if you need more debug information.
> >
> > Please help.
>
> As Hannes guessed, may be it is really the missing
> flags = FIB_LOOKUP_NOREF in ipmr_fib_lookup() when calling
> fib_rules_lookup(), we have an atomic_inc_not_zero() there that
> can stop to work after 4G lookups when rule's refcnt reaches 0.
> As result, fib_rules_lookup() can start to return -ESRCH.
I guess we should just try. I somehow forgot to look after that. Thanks
for reminding, Julian.
Bob, can you try with this patch again?
diff --git a/net/ipv4/ipmr.c b/net/ipv4/ipmr.c
index 421a249..b9b3472 100644
--- a/net/ipv4/ipmr.c
+++ b/net/ipv4/ipmr.c
@@ -157,9 +157,12 @@ static struct mr_table *ipmr_get_table(struct net *net, u32 id)
static int ipmr_fib_lookup(struct net *net, struct flowi4 *flp4,
struct mr_table **mrt)
{
- struct ipmr_result res;
- struct fib_lookup_arg arg = { .result = &res};
int err;
+ struct ipmr_result res;
+ struct fib_lookup_arg arg = {
+ .result = &res,
+ .flags = FIB_LOOKUP_NOREF,
+ };
err = fib_rules_lookup(net->ipv4.mr_rules_ops,
flowi4_to_flowi(flp4), 0, &arg);
next reply other threads:[~2014-01-07 17:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 17:01 Bob Falken [this message]
2014-01-07 17:43 ` Multicast routing stops functioning after 4G multicast packets recived Hannes Frederic Sowa
2014-01-07 20:11 ` Hannes Frederic Sowa
2014-01-07 20:20 ` Hannes Frederic Sowa
2014-01-07 20:26 ` Eric Dumazet
2014-01-07 20:29 ` Hannes Frederic Sowa
-- strict thread matches above, loose matches on Subject: below --
2014-01-12 0:25 Bob Falken
2014-01-09 20:14 Bob Falken
2014-01-10 6:36 ` Hannes Frederic Sowa
2014-01-10 7:01 ` Eric Dumazet
2014-01-10 7:10 ` Hannes Frederic Sowa
2014-01-10 7:32 ` Eric Dumazet
2014-01-10 7:43 ` Hannes Frederic Sowa
2014-01-10 7:50 ` Hannes Frederic Sowa
2014-01-12 7:42 ` Hannes Frederic Sowa
2014-01-13 0:56 ` Eric Dumazet
2014-01-04 18:53 Bob Falken
2013-12-21 22:35 Bob Falken
2014-01-03 7:37 ` Hannes Frederic Sowa
2013-12-19 16:28 Bob Falken
2013-12-19 17:24 ` Eric Dumazet
2013-12-19 17:32 ` Hannes Frederic Sowa
2013-12-22 3:10 ` Hannes Frederic Sowa
2013-12-19 14:48 Bob Falken
2013-12-19 15:09 ` Hannes Frederic Sowa
2013-12-19 15:15 ` Ben Greear
2013-12-19 15:48 ` Hannes Frederic Sowa
2014-01-04 19:55 ` Julian Anastasov
2014-01-04 23:38 ` Hannes Frederic Sowa
2014-01-05 8:56 ` Julian Anastasov
2014-01-05 10:41 ` Hannes Frederic Sowa
2014-01-05 19:12 ` Eric Dumazet
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=20140107170145.317040@gmx.com \
--to=netfestivalhavefun@gmx.com \
--cc=hannes@stressinduktion.org \
--cc=ja@ssi.bg \
--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).