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-maint v2] batman-adv: lock crc access in bridge loop avoidance
Date: Sun, 13 Sep 2015 18:20:12 +0800 [thread overview]
Message-ID: <2662065.oem7IOexWu@voltaire> (raw)
In-Reply-To: <1441987453-5553-1-git-send-email-sw@simonwunderlich.de>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
On Friday, September 11, 2015 18:04:13 Simon Wunderlich wrote:
> We have found some networks in which nodes were constantly requesting
> other nodes BLA claim tables to synchronize, just to ask for that again
> once completed. The reason was that the crc checksum of the asked nodes
> were out of sync due to missing locking and multiple writes to the same
> crc checksum when adding/removing entries. Therefore the asked nodes
> constantly reported the wrong crc, which caused repeating requests.
>
> To avoid multiple functions changing a backbone gateways crc entry at
> the same time, lock it using a spinlock.
>
> Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de>
> Tested-by: Alfons Name <AlfonsName@web.de>
> ---
> Changes to PATCH-maint:
> * fix spin_lock -> spin_unlock in claim table printing (thanks Petr)
> ---
> net/batman-adv/bridge_loop_avoidance.c | 35
> +++++++++++++++++++++++++++++-----
> net/batman-adv/types.h | 2 ++
> 2 files changed, 32 insertions(+), 5 deletions(-)
Applied in revision b307e72.
Thanks,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-09-13 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 16:04 [B.A.T.M.A.N.] [PATCH-maint v2] batman-adv: lock crc access in bridge loop avoidance Simon Wunderlich
2015-09-13 10:20 ` 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=2662065.oem7IOexWu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.