From: Simon Wunderlich <sw@simonwunderlich.de>
To: Andreas Pape <apape@phoenixcontact.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: handle race condition for claims also in batadv_bla_rx
Date: Tue, 09 May 2017 17:50:41 +0200 [thread overview]
Message-ID: <38318850.GE51cWUxAf@prime> (raw)
In-Reply-To: <20170428202610.27022-1-sw@simonwunderlich.de>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
On Friday, April 28, 2017 10:26:10 PM CEST Simon Wunderlich wrote:
> From: Andreas Pape <apape@phoenixcontact.com>
>
> Like in the case of the patch for batadv_bla_tx to handle a race
> condition when claiming a mac address for bla, a similar situation
> can occur when claiming is triggered via batadv_bla_rx. This patch
> solves this with a similar approach as for batadv_bla_tx.
>
> Signed-off-by: Andreas Pape <apape@phoenixcontact.com>
Hi Andreas,
thanks again for the patch - in general, I think this looks good, although I
don't follow completely where you saw that. Can you describe the scenario a
little more?
We usually don't process packets from the mesh sent by nodes on the same LAN
segment - we look at the originator and check the BLA group using
batadv_check_claim_group().
There are two things which we could improve documentation-wise:
1.) Have some kernel doc batadv_tt_local_has_timed_out - we want to have
kerneldoc for every new function we add.
2.) Describe the scenario in a comment in batadv_bla_rx(). I find the comment
not too convincing, see above.
Again, if this situation is really happening then I believe this patch
provides a good solution which I'd like to adopt. :)
Thank you,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-05-09 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 20:26 [B.A.T.M.A.N.] [PATCH] batman-adv: handle race condition for claims also in batadv_bla_rx Simon Wunderlich
2017-05-09 15:50 ` Simon Wunderlich [this message]
2017-05-10 5:45 ` [B.A.T.M.A.N.] Antwort: " Andreas Pape
2019-06-09 11:28 ` Sven Eckelmann
2019-07-02 8:39 ` Antwort: " Andreas Pape
2019-07-02 8:41 ` Sven Eckelmann
-- strict thread matches above, loose matches on Subject: below --
2017-06-01 15:11 [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: do not add loop detection mac addresses to global tt Simon Wunderlich
2017-06-01 15:11 ` [B.A.T.M.A.N.] [PATCH] batman-adv: handle race condition for claims also in batadv_bla_rx Simon Wunderlich
2017-06-01 15:12 ` Simon Wunderlich
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=38318850.GE51cWUxAf@prime \
--to=sw@simonwunderlich.de \
--cc=apape@phoenixcontact.com \
--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.