All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 2894f1: monitor/att: Attempt to reload if database is empty
Date: Wed, 25 May 2022 13:07:10 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/79fe52-1ffd74@github.com> (raw)

  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: 2894f1392fbe5e570039e9a753c7065cb8fcbf01
      https://github.com/bluez/bluez/commit/2894f1392fbe5e570039e9a753c7065cb8fcbf01
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2022-05-25 (Wed, 25 May 2022)

  Changed paths:
    M monitor/att.c

  Log Message:
  -----------
  monitor/att: Attempt to reload if database is empty

If database is empty attempt to reload since the daemon may have
updated its cache in the meantime.


  Commit: 1ffd74a6d4212a165763dc53e58a1b49b6fc5a98
      https://github.com/bluez/bluez/commit/1ffd74a6d4212a165763dc53e58a1b49b6fc5a98
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2022-05-25 (Wed, 25 May 2022)

  Changed paths:
    M monitor/att.c
    M monitor/l2cap.h

  Log Message:
  -----------
  monitor/att: Fix parsing of notifications

If there are multiple notifications in the same frame the callback may
alter it when using l2cap_frame_pull helpers, so instead this passes a
cloned frame with just the expected length so callbacks cannot alter
original frame.


Compare: https://github.com/bluez/bluez/compare/79fe529d6485...1ffd74a6d421

                 reply	other threads:[~2022-05-25 20:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bluez/bluez/push/refs/heads/master/79fe52-1ffd74@github.com \
    --to=noreply@github.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.