Netdev List
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: Sebastian Ott <sebott@linux.vnet.ibm.com>,
	Xin Long <lucien.xin@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Haidong Li <haili@redhat.com>, Ivan Vecera <cera@cera.cz>,
	Stephen Hemminger <stephen@networkplumber.org>,
	network dev <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: Oops with commit 6d18c73 bridge: start hello_timer when enabling KERNEL_STP in br_stp_start
Date: Thu, 1 Jun 2017 17:16:23 +0300	[thread overview]
Message-ID: <edd9b7f0-0345-975e-dc97-d5261134c7b4@cumulusnetworks.com> (raw)
In-Reply-To: <a6495939-350d-31a4-88db-852344a19a02@cumulusnetworks.com>

On 01/06/17 17:00, Nikolay Aleksandrov wrote:
> On 01/06/17 15:34, Sebastian Ott wrote:
>> On Thu, 1 Jun 2017, Xin Long wrote:
>>> On Thu, Jun 1, 2017 at 12:32 AM, Sebastian Ott
>>> <sebott@linux.vnet.ibm.com> wrote:
>>>> [...]
>>> I couldn't see any bridge-related thing here, and it couldn't be reproduced
>>> with virbr0 (stp=1) on my box (on both s390x and x86_64), I guess there
>>> is something else in you machine.
>>>
>>> With the latest upstream kernel, can you remove libvirt (virbr0) and boot your
>>> machine normally, then:
>>> # brctl addbr br0
>>> # ip link set br0 up
>>> # brctl stp br0 on
>>>
>>> to check if it will still hang.
>>
>> Nope. That doesn't hang.
>>
>>
>>> If it can't be reproduced in this way, pls add this on your kernel:
>>>
>>> --- a/net/bridge/br_stp_if.c
>>> +++ b/net/bridge/br_stp_if.c
>>> @@ -178,9 +178,11 @@ static void br_stp_start(struct net_bridge *br)
>>>                 br->stp_enabled = BR_KERNEL_STP;
>>>                 br_debug(br, "using kernel STP\n");
>>>
>>> +               WARN_ON(1);
>>>                 /* To start timers on any ports left in blocking */
>>>                 mod_timer(&br->hello_timer, jiffies + br->hello_time);
>>>                 br_port_state_selection(br);
>>> +               pr_warn("hello timer start done\n");
>>>         }
>>>
>>>         spin_unlock_bh(&br->lock);
>>> diff --git a/net/bridge/br_stp_timer.c b/net/bridge/br_stp_timer.c
>>> index 60b6fe2..c98b3e5 100644
>>> --- a/net/bridge/br_stp_timer.c
>>> +++ b/net/bridge/br_stp_timer.c
>>> @@ -40,7 +40,7 @@ static void br_hello_timer_expired(unsigned long arg)
>>>         if (br->dev->flags & IFF_UP) {
>>>                 br_config_bpdu_generation(br);
>>>
>>> -               if (br->stp_enabled == BR_KERNEL_STP)
>>> +               if (br->stp_enabled != BR_USER_STP)
>>>                         mod_timer(&br->hello_timer,
>>>                                   round_jiffies(jiffies + br->hello_time));
>>>
>>>
>>> let's see if it hangs when starting the timer. Thanks.
>>
>> No hang either:
>>
> [snip]
> Could you please try the patch below ?
> 
> ---
> 
> diff --git a/net/bridge/br_stp_if.c b/net/bridge/br_stp_if.c
> index 4efd5d54498a..89110319ef0f 100644
> --- a/net/bridge/br_stp_if.c
> +++ b/net/bridge/br_stp_if.c
> @@ -173,7 +173,8 @@ static void br_stp_start(struct net_bridge *br)
>  		br_debug(br, "using kernel STP\n");
>  
>  		/* To start timers on any ports left in blocking */
> -		mod_timer(&br->hello_timer, jiffies + br->hello_time);
> +		if (br->dev->flags & IFF_UP)
> +			mod_timer(&br->hello_timer, jiffies + br->hello_time);
>  		br_port_state_selection(br);
>  	}
>  
> 

Ah nevermind, this patch reverts it back to the previous state.

  reply	other threads:[~2017-06-01 14:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31 16:32 Oops with commit 6d18c73 bridge: start hello_timer when enabling KERNEL_STP in br_stp_start Sebastian Ott
2017-06-01  7:42 ` Xin Long
2017-06-01 12:34   ` Sebastian Ott
2017-06-01 14:00     ` Nikolay Aleksandrov
2017-06-01 14:16       ` Nikolay Aleksandrov [this message]
2017-06-01 14:45         ` Nikolay Aleksandrov
2017-06-01 15:07           ` [PATCH net] net: bridge: start hello timer only if device is up Nikolay Aleksandrov
2017-06-01 16:31             ` David Miller
2017-06-01 19:44             ` Sebastian Ott

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=edd9b7f0-0345-975e-dc97-d5261134c7b4@cumulusnetworks.com \
    --to=nikolay@cumulusnetworks.com \
    --cc=cera@cera.cz \
    --cc=davem@davemloft.net \
    --cc=haili@redhat.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=sebott@linux.vnet.ibm.com \
    --cc=stephen@networkplumber.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