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.
This commit is contained in:
Jonas Maes 2022-06-10 17:29:02 +02:00 committed by Brian Gix
parent 949898cc5e
commit 71560e1286

View File

@ -725,7 +725,6 @@ static bool send_tx(struct mesh_io *io, struct mesh_io_send_info *info,
{
struct mesh_io_private *pvt = io->pvt;
struct tx_pkt *tx;
bool sending = false;
if (!info || !data || !len || len > sizeof(tx->pkt))
return false;
@ -739,23 +738,21 @@ static bool send_tx(struct mesh_io *io, struct mesh_io_send_info *info,
if (info->type == MESH_IO_TIMING_TYPE_POLL_RSP)
l_queue_push_head(pvt->tx_pkts, tx);
else {
if (pvt->tx)
sending = true;
else
sending = !l_queue_isempty(pvt->tx_pkts);
l_queue_push_tail(pvt->tx_pkts, tx);
/*
* If transmitter is idle, send packets at least twice to
* guard against in-line cancelation of HCI command chain.
*/
if (info->type == MESH_IO_TIMING_TYPE_GENERAL && !sending &&
tx->info.u.gen.cnt == 1)
if (info->type == MESH_IO_TIMING_TYPE_GENERAL &&
!pvt->tx &&
l_queue_isempty(pvt->tx_pkts) &&
tx->info.u.gen.cnt == 1)
tx->info.u.gen.cnt++;
l_queue_push_tail(pvt->tx_pkts, tx);
}
if (!sending) {
/* If not already sending, schedule the tx worker */
if (!pvt->tx) {
l_timeout_remove(pvt->tx_timeout);
pvt->tx_timeout = NULL;
l_idle_oneshot(tx_worker, pvt, NULL);