linux-kernel - RE: [PATCH 4.4 009/115] Bluetooth: btusb: driver to enable the usb-wakeup feature

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] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 21 Dec 2017 19:23:27 +0000
From:   "Ghorai, Sukumar" <sukumar.ghorai@...el.com>
To:     Brian Norris <briannorris@...omium.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        Marcel Holtmann <marcel@...tmann.org>,
        "Oliver Neukum" <oneukum@...e.com>,
        Guenter Roeck <linux@...ck-us.net>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
CC:     "Bag, Amit K" <amit.k.bag@...el.com>,
        Matthias Kaehlcke <mka@...omium.org>,
        Todd Broch <tbroch@...omium.org>,
        Rajat Jain <rajatja@...omium.org>,
        Miao Chou <mcchou@...omium.org>,
        "Rao Pv, Sadashiva" <sadashiva.rao.pv@...el.com>
Subject: RE: [PATCH 4.4 009/115] Bluetooth: btusb: driver to enable the
 usb-wakeup feature

>> >Could you ever? If not, that looks like a feature request to me...
>> Agree, feature request... however  we need this feature for rapid use of
>Bluetooth LE devices.
>
>Is that what -stable is for now? For getting your pet feature enabled more
>quickly? I thought that's what Linaro was for, or something like that.
>
>Besides the poor reasoning of the above (IMO): isn't that something you can also
>configure in user space? So, upgrade user space (e.g., BlueZ) to resolve the
>regressions that have been reported, then write the appropriate udev rules to
>turn this on? Or is that too "slow" for you?
Free to take decision..

I understand this feature is creating instability in other area. However -
1. the  problem will remain same when enable the usb-wakeup feature form
kernel or user-space or udev rule, and as long LE device is connected.
2. Even the behavior is same in existing stable code, when connect the
Bluetooth BR/EDR mouse (io device), as It will enable the usb-wakeup feature/flag,

>
>Brian