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: [PATCH BlueZ v4 0/5] Use composition data to validate app against the node
Date: Thu, 25 Jul 2019 21:49:28 +0200	[thread overview]
Message-ID: <20190725194933.7321-1-michal.lowas-rzechonek@silvair.com> (raw)

+ Fix setting app_path and owner during Attach()
+ Fix typo CompanyID property validation
+ Added comments about temporary node usage during Attach()
+ Keep element's Location property optional according to API
  documentation

---

This patchset streamlines app validation by creating a temporary node
during Attach, Join and CreateNetwork calls, then validating its
composition data to:
 - fit in Config Model Composition Data Get message
 - declare mandatory models on primary element
 - declare consecutive element indexes

During Attach call, temporary composition data is also compared with
data generated for existing node, guaranteeing immutablity required by
the specification.

Michał Lowas-Rzechonek (5):
  mesh: Convert void pointers to anonymous unions in managed_obj_request
  mesh: Validate application by comparing composition data
  mesh: Keep element and model lists sorted and unique
  mesh: Check that element indexes are consecutive
  mesh: Check that config server is present in primary element

 mesh/mesh-defs.h |   2 +
 mesh/node.c      | 558 ++++++++++++++++++++++++-----------------------
 2 files changed, 292 insertions(+), 268 deletions(-)

-- 
2.22.0


             reply	other threads:[~2019-07-25 19:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25 19:49 Michał Lowas-Rzechonek [this message]
2019-07-25 19:49 ` [PATCH BlueZ v4 1/5] mesh: Convert void pointers to anonymous unions in managed_obj_request Michał Lowas-Rzechonek
2019-07-25 19:49 ` [PATCH BlueZ v4 2/5] mesh: Validate application by comparing composition data Michał Lowas-Rzechonek
2019-07-26  3:58   ` Stotland, Inga
2019-07-25 19:49 ` [PATCH BlueZ v4 3/5] mesh: Keep element and model lists sorted and unique Michał Lowas-Rzechonek
2019-07-25 19:49 ` [PATCH BlueZ v4 4/5] mesh: Check that element indexes are consecutive Michał Lowas-Rzechonek
2019-07-25 19:49 ` [PATCH BlueZ v4 5/5] mesh: Check that config server is present in primary element 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=20190725194933.7321-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).