Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   =?UTF-8?q?Micha=C5=82=20Lowas-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
Message-Id: <20190717195328.16322-1-michal.lowas-rzechonek@silvair.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

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