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  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 20:15:23 +0000
From:   "Ghorai, Sukumar" <>
To:     Guenter Roeck <>
CC:     Brian Norris <>,
        "" <>,
        "" <>,
        Marcel Holtmann <>,
        "Oliver Neukum" <>,
        "" <>,
        "Bag, Amit K" <>,
        Matthias Kaehlcke <>,
        Todd Broch <>,
        Rajat Jain <>,
        "Miao Chou" <>,
        "Rao Pv, Sadashiva" <>
Subject: RE: [PATCH 4.4 009/115] Bluetooth: btusb: driver to enable the
 usb-wakeup feature

>> 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
>There is a slight difference of leaving the decision to the user (or to
>userspace) or forcing it down the throat of everyone by adding it to the kernel.
>Your statement "I understand this feature is creating instability in other area"
>should really be a wakeup call. It almost sounds like you are aware that it is
>causing problems, but you don't care because it fits _your_ needs. I hope that is
>not the case, but if it is, please keep in mind that you are not the only user of the
>Linux kernel.
No I don't know what is the problem here...
As mentioned, keeping wake up enable(default) is same as BR/EDR mouse connected.
Hence you will see the same platform behavior when BR/EDR mouse connected, and 
Without this patch.


Powered by blists - more mailing lists