linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michał Lowas-Rzechonek" <michal.lowas-rzechonek@silvair.com>
To: linux-bluetooth@vger.kernel.org
Subject: [RFC BlueZ 0/2] Use composition data to validate app against the node
Date: Wed, 17 Jul 2019 21:53:26 +0200	[thread overview]
Message-ID: <20190717195328.16322-1-michal.lowas-rzechonek@silvair.com> (raw)

This patchset streamlines app validation by creating a temporary node
during Join, CreateNetwork and ImportLocalNode calls and then
comparing temporary composition data with one generated for already
existing node.

In case of Attach call, the temporary node is simply added to the list.

TODO: Composition data generation needs to validate node structure,
checking that:
 - primary element exists
 - mandatory models are where they should be
 - there are no gaps in element indexes
 - ... possibly a few more things

Michał Lowas-Rzechonek (2):
  mesh: Keep model list sorted and unique
  mesh: Validate application by comparing composition data

 mesh/cfgmod-server.c |  14 +-
 mesh/mesh-defs.h     |   2 +
 mesh/node.c          | 453 ++++++++++++++++++-------------------------
 3 files changed, 198 insertions(+), 271 deletions(-)

-- 
2.22.0


             reply	other threads:[~2019-07-17 19:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17 19:53 Michał Lowas-Rzechonek [this message]
2019-07-17 19:53 ` [RFC BlueZ 1/2] mesh: Keep model list sorted and unique Michał Lowas-Rzechonek
2019-07-17 19:53 ` [RFC BlueZ 2/2] mesh: Validate application by comparing composition data Michał Lowas-Rzechonek

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=20190717195328.16322-1-michal.lowas-rzechonek@silvair.com \
    --to=michal.lowas-rzechonek@silvair.com \
    --cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).