From: "Bob Falken" <NetFestivalHaveFun@gmx•com>
To: "Hannes Frederic Sowa" <hannes@stressinduktion•org>
Cc: "Eric Dumazet" <eric.dumazet@gmail•com>,
"Ben Greear" <greearb@candelatech•com>,
netdev@vger•kernel.org
Subject: Re: Multicast routing stops functioning after 4G multicast packets recived.
Date: Sat, 04 Jan 2014 19:53:13 +0100 [thread overview]
Message-ID: <20140104185313.18790@gmx.com> (raw)
Hello, I compiled kernel 3.2.53 with the lates stable grsec patch, and enabled the CONFIG_PAX_REFCOUNT.
Unfortuantly the server lockedup after about 13hours so i did not get a dmesg event. forgot to disable vty blank, so don't know the reason for the server lockup.(could just be a bad kernel build).
I have rebuildt the kernel and will report back with the result, should have some results in about 16hours, unless the server locksup again.
----- Original Message -----
From: Hannes Frederic Sowa
Sent: 01/03/14 08:37 AM
To: Bob Falken
Subject: Re: Multicast routing stops functioning after 4G multicast packets recived.
On Sat, Dec 21, 2013 at 11:35:00PM +0100, Bob Falken wrote:
> On Thu, Dec 19, 2013 at 09:24:18AM -0800, Eric Dumazet wrote:
> > On Thu, 2013-12-19 at 17:28 +0100, Bob Falken wrote:
> > > The only reason why i give information about 2.6.36.4 is that its the
> > > only latest kernel that was functioning properly.
> > > i.e kernel >= 2.6.37 is not woking. so its a bisecting of the kernel
> > > versions to help a coder see when/where the isse was implemented in
> > > the kernel.
> > >
> > > I do not need a backport patch for an old kernel, I generally only
> > > need the issue looked into and get fixed so that I dont have to use an
> > > old kernel. :)
> > >
> > > I have no issue reproducing the issue on the recent kernels. however i
> > > have not tried the GIT kernel.
> > >
> > > I restarted the server just a moment ago. i will install and run
> > > dropwatch and provide feedback in about 17hours.
> >
> > You said that "cat /proc/net/ip_mr_cache" gives nothing at all after
> > 2^32 packets ?
> >
> > Thats a bit scary ... maybe a 32bit refcnt overflow, because of some
> > imbalance...
>
> That's my thought, too. :/
>
> The ipmr.c rcu conversion happend in 2.6.37.
>
Just as a follow-up. You could verify if we actually have a refcount overflow
if you try a grsec kernel with PAX_REFCOUNT enabled. If a refcoount overflow
happens, dmesg should show then.
Greetings,
Hannes
next reply other threads:[~2014-01-04 18:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 18:53 Bob Falken [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-12 0:25 Multicast routing stops functioning after 4G multicast packets recived 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-07 17:01 Bob Falken
2014-01-07 17:43 ` 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
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=20140104185313.18790@gmx.com \
--to=netfestivalhavefun@gmx$(echo .)com \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=greearb@candelatech$(echo .)com \
--cc=hannes@stressinduktion$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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