From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Cong Wang <amwang@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
netdev@vger.kernel.org
Subject: Re: mod_timer: list_add corruption: WARNING: CPU: 1 PID: 0 at lib/list_debug.c:33 __list_add+0xbe/0xd0()
Date: Sat, 20 Jul 2013 00:16:23 +0530 [thread overview]
Message-ID: <51E9897F.5030205@linux.vnet.ibm.com> (raw)
In-Reply-To: <1374254778.26476.18.camel@edumazet-glaptop>
On 07/19/2013 10:56 PM, Eric Dumazet wrote:
> On Fri, 2013-07-19 at 18:38 +0200, Thomas Gleixner wrote:
>> On Fri, 19 Jul 2013, Eric Dumazet wrote:
>>>
>>> I guess following should help
>>
>> Applying the empty patch does not work very well. Could you try again
>> after the caffeine reached your brain, please ? :)
>
> hmm, right ;)
>
This patch fixes the issue for me - the system has been idle for more
than an hour now without any problems (earlier, i used to get the traces
within 5 minutes of idle time).
Thanks a lot for the fix!
Tested-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
Regards,
Srivatsa S. Bhat
> diff --git a/net/bridge/br_multicast.c b/net/bridge/br_multicast.c
> index 69af490..4b99c9a 100644
> --- a/net/bridge/br_multicast.c
> +++ b/net/bridge/br_multicast.c
> @@ -619,6 +619,9 @@ rehash:
> mp->br = br;
> mp->addr = *group;
>
> + setup_timer(&mp->timer, br_multicast_group_expired,
> + (unsigned long)mp);
> +
> hlist_add_head_rcu(&mp->hlist[mdb->ver], &mdb->mhash[hash]);
> mdb->size++;
>
> @@ -1126,7 +1129,6 @@ static int br_ip4_multicast_query(struct net_bridge *br,
> if (!mp)
> goto out;
>
> - setup_timer(&mp->timer, br_multicast_group_expired, (unsigned long)mp);
> mod_timer(&mp->timer, now + br->multicast_membership_interval);
> mp->timer_armed = true;
>
> @@ -1204,7 +1206,6 @@ static int br_ip6_multicast_query(struct net_bridge *br,
> if (!mp)
> goto out;
>
> - setup_timer(&mp->timer, br_multicast_group_expired, (unsigned long)mp);
> mod_timer(&mp->timer, now + br->multicast_membership_interval);
> mp->timer_armed = true;
>
next prev parent reply other threads:[~2013-07-19 18:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 14:25 mod_timer: list_add corruption: WARNING: CPU: 1 PID: 0 at lib/list_debug.c:33 __list_add+0xbe/0xd0() Srivatsa S. Bhat
2013-07-19 8:22 ` Srivatsa S. Bhat
2013-07-19 9:08 ` Srivatsa S. Bhat
2013-07-19 11:25 ` Thomas Gleixner
2013-07-19 11:47 ` Srivatsa S. Bhat
2013-07-19 13:40 ` Thomas Gleixner
2013-07-19 13:51 ` Eric Dumazet
2013-07-19 16:38 ` Thomas Gleixner
2013-07-19 17:26 ` Eric Dumazet
2013-07-19 18:46 ` Srivatsa S. Bhat [this message]
2013-07-20 3:07 ` [PATCH] bridge: do not call setup_timer() multiple times Eric Dumazet
2013-07-20 5:13 ` 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=51E9897F.5030205@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=amwang@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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).