From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ 0/2] Fix AppKey deletion
Date: Tue, 14 Jan 2020 14:37:18 +0000 [thread overview]
Message-ID: <2f16da308b1fe1f173cdd761d8e630774414ed11.camel@intel.com> (raw)
In-Reply-To: <20200110014145.1785-1-inga.stotland@intel.com>
Patchset Applied
On Thu, 2020-01-09 at 17:41 -0800, Inga Stotland wrote:
> This patch set contains fixes for:
> - deleting individual app key deletion as a result receiving
> Config AppKey Delete message. The fix removes a dulpicate attempt
> to write to config storage and some function call simplifications
>
> - deleting a number of appkeys as a result of receiving
> Config NetKey Delete message. When deleting multiple entries from a
> queue, do not use queue iteration mechanism as the deletion of
> multiple entries may result in seg fault. Instead, find and delete
> bound keys one by one until none are found.
>
>
> Inga Stotland (2):
> mesh: Fix logic in AppKey deletion
> mesh: Fix wholesale deletion of appkeys bound to a netkey
>
> mesh/appkey.c | 32 ++++++++++++++++++++++++--------
> mesh/node.c | 29 ++---------------------------
> mesh/node.h | 4 ++--
> 3 files changed, 28 insertions(+), 37 deletions(-)
>
prev parent reply other threads:[~2020-01-14 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 1:41 [PATCH BlueZ 0/2] Fix AppKey deletion Inga Stotland
2020-01-10 1:41 ` [PATCH BlueZ 1/2] mesh: Fix logic in " Inga Stotland
2020-01-10 1:41 ` [PATCH BlueZ 2/2] mesh: Fix wholesale deletion of appkeys bound to a netkey Inga Stotland
2020-01-14 14:37 ` Gix, Brian [this message]
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=2f16da308b1fe1f173cdd761d8e630774414ed11.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.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).