linux-kernel - Re: [PATCH 2/2] Bluetooth: btmrvl: don't send data to firmware while processing suspend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <99551394-8D9D-4D08-9010-DE1D00851B79@holtmann.org>
Date:	Wed, 6 Jan 2016 07:24:07 -0800
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Amitkumar Karwar <akarwar@...vell.com>
Cc:	linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
	Chin-Ran Lo <crlo@...vell.com>
Subject: Re: [PATCH 2/2] Bluetooth: btmrvl: don't send data to firmware while processing suspend

Hi Amitkumar,

> Usually when driver sends data to firmware it receives TX_DONE
> (DN_LD_HOST_INT_STATUS) interrupt from firmware right away.
> It's also observed that some times the fireware could delay
> sending DN_LD_HOST_INT_STATUS interrupt. If driver sends data to
> firmware during suspend processing and the TX_DONE interrupt is
> delayed, it may come back at wrong time when SDIO host driver is
> in the middle of suspending.
> 
> Block any data from stack while suspending. Also skip sending
> data that are already in driver tx_queue.
> 
> Don't purge the skb queue on suspend to avoid intermittent music
> after system resumes from S3.
> 
> Signed-off-by: Chin-Ran Lo <crlo@...vell.com>
> Signed-off-by: Amitkumar Karwar <akarwar@...vell.com>
> ---
> drivers/bluetooth/btmrvl_drv.h  |  1 +
> drivers/bluetooth/btmrvl_main.c | 11 +++++++++--
> drivers/bluetooth/btmrvl_sdio.c |  3 ++-
> 3 files changed, 12 insertions(+), 3 deletions(-)

patch has been applied to bluetooth-next tree.

Regards

Marcel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/