From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Antonio Quartulli <antonio@open-mesh.com>,
Antonio Quartulli <ordex@autistici.org>
Subject: Re: [B.A.T.M.A.N.] [PATCHv9 1/2] batman-adv: lock around TT operations to avoid sending inconsistent data
Date: Wed, 7 Aug 2013 19:27:22 +0800 [thread overview]
Message-ID: <201308071927.22294.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1375215385-606-2-git-send-email-ordex@autistici.org>
On Wednesday, July 31, 2013 04:16:24 Antonio Quartulli wrote:
> From: Antonio Quartulli <antonio@open-mesh.com>
>
> A TT response may be prepared and sent while the local or
> global translation table is getting updated.
>
> The worst case is when one of the tables is accessed after
> its content has been recently updated but the metadata
> (TTVN/CRC) has not yet. In this case the reader will get a
> table content which does not match the TTVN/CRC.
> This will lead to an inconsistent state and so to a TT
> recovery.
>
> To avoid entering this situation, put a lock around those TT
> operations recomputing the metadata and around the TT
> Response creation (the latter is the only reader that
> accesses the metadata together with the table).
>
> Signed-off-by: Antonio Quartulli <antonio@open-mesh.com>
> ---
> main.c | 1 +
> originator.c | 1 +
> translation-table.c | 23 +++++++++++++++++++----
> types.h | 13 +++++++++++++
> 4 files changed, 34 insertions(+), 4 deletions(-)
Applied in revision 1583626.
Thanks,
Marek
next prev parent reply other threads:[~2013-08-07 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 20:16 [B.A.T.M.A.N.] [PATCHv9 0/2] per-VLAN TT CRC Antonio Quartulli
2013-07-30 20:16 ` [B.A.T.M.A.N.] [PATCHv9 1/2] batman-adv: lock around TT operations to avoid sending inconsistent data Antonio Quartulli
2013-08-07 11:27 ` Marek Lindner [this message]
2013-07-30 20:16 ` [B.A.T.M.A.N.] [PATCHv9 2/2] batman-adv: make the TT CRC logic VLAN specific Antonio Quartulli
2013-08-07 11:29 ` Marek Lindner
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=201308071927.22294.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=antonio@open-mesh.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=ordex@autistici.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