From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Deactive TO_BE_ACTIVATED hardif on shutdown
Date: Sun, 27 Mar 2016 15:08:39 +0800 [thread overview]
Message-ID: <3016125.hgzoRVfCNO@voltaire> (raw)
In-Reply-To: <1458392121-23608-1-git-send-email-sven@narfation.org>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
On Saturday, March 19, 2016 13:55:21 Sven Eckelmann wrote:
> The shutdown of an batman-adv interface can happen with one of its slave
> interfaces still being in the BATADV_IF_TO_BE_ACTIVATED state. A possible
> reason for it is that the routing algorithm BATMAN_V was selected and
> batadv_schedule_bat_ogm was not yet called for this interface. This slave
> interface still has to be set to BATADV_IF_INACTIVE or the batman-adv
> interface will never reduce its usage counter and thus never gets shutdown.
>
> This problem can be simulated via:
>
> $ modprobe dummy
> $ modprobe batman-adv routing_algo=BATMAN_V
> $ ip link add bat0 type batadv
> $ ip link set dummy0 master bat0
> $ ip link set dummy0 up
> $ ip link del bat0
> unregister_netdevice: waiting for bat0 to become free. Usage count = 3
>
> Fixes: 88861ea9acb7 ("[batman-adv] replacing if up/down timer with kernel
> notifications") Reported-by: Matthias Schiffer
> <mschiffer@universe-factory.net>
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
Applied in revision fbb98aa.
Thanks,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-03-27 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 12:55 [B.A.T.M.A.N.] [PATCH] batman-adv: Deactive TO_BE_ACTIVATED hardif on shutdown Sven Eckelmann
2016-03-19 13:24 ` Sven Eckelmann
2016-03-27 7:08 ` Marek Lindner [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=3016125.hgzoRVfCNO@voltaire \
--to=mareklindner@neomailbox.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.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