From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DA509C169C4 for ; Wed, 6 Feb 2019 07:31:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AB2A0218A1 for ; Wed, 6 Feb 2019 07:31:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726804AbfBFHb1 (ORCPT ); Wed, 6 Feb 2019 02:31:27 -0500 Received: from mga12.intel.com ([192.55.52.136]:40201 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725897AbfBFHb0 (ORCPT ); Wed, 6 Feb 2019 02:31:26 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Feb 2019 23:31:26 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,339,1544515200"; d="scan'208";a="131449162" Received: from ingas-nuc1.sea.intel.com ([10.254.59.164]) by FMSMGA003.fm.intel.com with ESMTP; 05 Feb 2019 23:31:26 -0800 From: Inga Stotland To: linux-bluetooth@vger.kernel.org Cc: brian.gix@intel.com, johan.hedberg@gmail.com, luiz.dentz@gmail.com, Inga Stotland Subject: [PATCH BlueZ 0/5] mesh: Save/restore network keys Date: Tue, 5 Feb 2019 23:31:10 -0800 Message-Id: <20190206073115.28232-1-inga.stotland@intel.com> X-Mailer: git-send-email 2.17.2 Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org This set of patches fixes the network key add/update processing. Network keys need to be saved to a local node configuration file when: - a new node is provisioned - new network key are added by a configuration client - existing network key is updated by a configuration client during key refresh procedure. Also, each saved network key is accompanied by a proper key refresh phase setting. Inga Stotland (5): mesh: Separate functions for net key add and update mesh: Add function to restore net key state from storage mesh: Declare internal functions as static mesh: Save key refresh phase state to node config file mesh: Save newly added or updated net key to config file mesh/cfgmod-server.c | 8 +- mesh/mesh-db.c | 178 +++++++++++++++++------------ mesh/mesh-db.h | 6 +- mesh/net.c | 262 ++++++++++++++++++++++++++----------------- mesh/net.h | 12 +- mesh/node.c | 19 +++- mesh/storage.c | 22 ++-- mesh/storage.h | 7 +- 8 files changed, 319 insertions(+), 195 deletions(-) -- 2.17.2