linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@codecoup.pl>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] gatt: Fix Acquire* reply handling
Date: Thu, 02 Apr 2020 10:02:27 +0200	[thread overview]
Message-ID: <5451372.4TLDOW9l6p@ix> (raw)
In-Reply-To: <20200401232733.10686-1-luiz.dentz@gmail.com>

Hi Luiz,

On Thursday, 2 April 2020 01:27:33 CEST Luiz Augusto von Dentz wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> Originally these operation did not set any owner_queue which caused
> them to crash if the attribute is freed before the respose, to fix that
> the reply will now check if owner_queue was reset to NULL which means
> the attribute is no longer available but the owner_queue was never set
> in the first place so this ensures they are now setup properly.
> ---
>  src/gatt-database.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/src/gatt-database.c b/src/gatt-database.c
> index 11d886c56..483c84341 100644
> --- a/src/gatt-database.c
> +++ b/src/gatt-database.c
> @@ -2485,8 +2485,8 @@ static struct pending_op *acquire_write(struct
> external_chrc *chrc, {
>  	struct pending_op *op;
> 
> -	op = pending_write_new(device, NULL, attrib, id, value, len, 0,
> -						link_type, false, 
false);
> +	op = pending_write_new(device, chrc->pending_writes, attrib, id, 
value,
> +				len, 0, link_type, false, false);
> 
>  	if (g_dbus_proxy_method_call(chrc->proxy, "AcquireWrite",
>  					acquire_write_setup,
> @@ -2618,6 +2618,7 @@ static uint8_t ccc_write_cb(struct pending_op *op,
> void *user_data) if (g_dbus_proxy_get_property(chrc->proxy,
> "NotifyAcquired", &iter)) { op->data.iov_base = (void *) chrc;
>  		op->data.iov_len = sizeof(chrc);
> +		op->owner_queue = chrc->pending_writes;
>  		if (g_dbus_proxy_method_call(chrc->proxy, "AcquireNotify",
>  						
acquire_notify_setup,
>  						
acquire_notify_reply,

Patch applied, thanks.

-- 
pozdrawiam
Szymon Janc



      reply	other threads:[~2020-04-02  8:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 23:27 [PATCH BlueZ] gatt: Fix Acquire* reply handling Luiz Augusto von Dentz
2020-04-02  8:02 ` Szymon Janc [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=5451372.4TLDOW9l6p@ix \
    --to=szymon.janc@codecoup.pl \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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).