From: BluezTestBot <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 949898: avdtp: Free discover when send_request returns error
Date: Tue, 21 Jun 2022 13:21:11 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/19ad43-71560e@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 949898cc5e7f0657dff91f799718e54dc4cde723
https://github.com/bluez/bluez/commit/949898cc5e7f0657dff91f799718e54dc4cde723
Author: Chengyi <zhaochengyi@uniontech.com>
Date: 2022-06-21 (Tue, 21 Jun 2022)
Changed paths:
M profiles/audio/avdtp.c
Log Message:
-----------
avdtp: Free discover when send_request returns error
When send_request returns an error, session->discover should
be released here, so that the next time the program enters
avdtp_discover, the -EBUSY error will not be returned.
Commit: 71560e12863ff1b133e421ef7dd25d20c8d83acc
https://github.com/bluez/bluez/commit/71560e12863ff1b133e421ef7dd25d20c8d83acc
Author: Jonas Maes <jonas@dptechnics.com>
Date: 2022-06-21 (Tue, 21 Jun 2022)
Changed paths:
M mesh/mesh-io-generic.c
Log Message:
-----------
mesh: Fix bug where bluetooth-meshd stops sending
When there is a backlog of mesh packets to be sent, the packet sender
Fix bug where bluetooth-meshd stops sending
When there is a backlog of mesh packets to be sent, the packet sender
incorrectly infers that the tx worker thread is already running
and therefore needn't be invoked. As a result, the mesh daemon will
sometimes stop broadcasting while there are still packets in the queue.
It will not resume broadcasting.
This patch will invoke the tx worker thread correctly in that case.
The logic to send packets at least twice when the transmitter is idle
was slightly modified accordingly, and should behave the same way as
before.
Compare: https://github.com/bluez/bluez/compare/19ad4310c9b4...71560e12863f
reply other threads:[~2022-06-21 20:21 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/19ad43-71560e@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 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).