linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: inga.stotland@intel.com, brian.gix@intel.com
Subject: [PATCH BlueZ v2 2/4] mesh: Fix leaked mesh_net allocation
Date: Fri, 22 May 2020 14:13:07 -0700	[thread overview]
Message-ID: <20200522211309.233824-3-brian.gix@intel.com> (raw)
In-Reply-To: <20200522211309.233824-1-brian.gix@intel.com>

---
 mesh/node.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/mesh/node.c b/mesh/node.c
index 49ba7c885..db888d27c 100644
--- a/mesh/node.c
+++ b/mesh/node.c
@@ -1313,8 +1313,6 @@ static bool add_local_node(struct mesh_node *node, uint16_t unicast, bool kr,
 				bool ivu, uint32_t iv_idx, uint8_t dev_key[16],
 				uint16_t net_key_idx, uint8_t net_key[16])
 {
-	node->net = mesh_net_new(node);
-
 	if (!nodes)
 		nodes = l_queue_new();
 
-- 
2.25.4


  parent reply	other threads:[~2020-05-22 21:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 21:13 [PATCH BlueZ v2 0/4] mesh: Static Analysis clean-up Brian Gix
2020-05-22 21:13 ` [PATCH BlueZ v2 1/4] mesh: Fix using uninitialized bytes Brian Gix
2020-05-22 21:13 ` Brian Gix [this message]
2020-05-22 23:37   ` [BlueZ,v2,2/4] mesh: Fix leaked mesh_net allocation bluez.test.bot
2020-05-22 21:13 ` [PATCH BlueZ v2 3/4] mesh: Fix leaked message reference Brian Gix
2020-05-22 23:37   ` [BlueZ,v2,3/4] " bluez.test.bot
2020-05-22 21:13 ` [PATCH BlueZ v2 4/4] mesh: Destroy PB-ADV queue when provisioning done Brian Gix
2020-05-22 23:37   ` [BlueZ,v2,4/4] " bluez.test.bot
2020-05-25 14:15 ` [PATCH BlueZ v2 0/4] mesh: Static Analysis clean-up Gix, Brian

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=20200522211309.233824-3-brian.gix@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).