Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: aunxvtkzZkObYkglWRKn6c0Mhie7qzen1N0aHr7f1AP8WTY88oNw12lMylqz3lBd9Bt0KAx4FF
 AaK6qmrMzp3Q==
IronPort-SDR: jWer0k92bQxX0YFrEXuBD2EY2FKEBpc6gzUNhoS5XQC8OPeTfDDkn3vXnJTYWLM8N84NClb2La
 iS5alrwpLNqA==
From:   Inga Stotland <inga.stotland@intel.com>
To:     linux-bluetooth@vger.kernel.org
Cc:     brian.gix@intel.com, przemyslaw.fierek@silvair.com,
        Inga Stotland <inga.stotland@intel.com>
Subject: [PATCH BlueZ 0/4] Put safeguards around Leave call
Date:   Mon,  8 Jun 2020 20:59:05 -0700
Message-Id: <20200609035909.51061-1-inga.stotland@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

This set of patches addresses the situation when an application
calls Leave() method on a node that has another incomplete
method call on Network interface associated with it.

The simple solution is to return error in response to Leave() method
if an application still owes the daemon either a reply to GetManagedObjects
request in case of Attach() or a reply to JoinComplete() in case of
Join(), Create() or Import()

Inga Stotland (4):
  mesh: Make "Busy" and "InProgress" to be distinct errors
  mesh: Add destroy callback to dbus_send_with_timeout()
  mesh: Add timeout to a get managed objects call
  mesh: Add "node is busy" check for Leave() method

 doc/mesh-api.txt |  4 +++-
 mesh/dbus.c      | 14 +++++++----
 mesh/dbus.h      |  1 +
 mesh/error.h     |  1 +
 mesh/manager.c   | 11 ++++-----
 mesh/mesh.c      | 17 +++++++------
 mesh/node.c      | 62 +++++++++++++++++++++++++++++-------------------
 mesh/node.h      |  2 +-
 8 files changed, 68 insertions(+), 44 deletions(-)

-- 
2.26.2