linux-kernel - Re: [PATCH v5.3-rc2] Bluetooth: hci_uart: check for missing tty operations

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, 1 Aug 2019 15:50:44 +0200
From:   Greg KH <greg@...ah.com>
To:     Sasha Levin <sashal@...nel.org>
Cc:     Marcel Holtmann <marcel@...tmann.org>,
        Vladis Dronov <vdronov@...hat.com>,
        torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
        linux-bluetooth@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH v5.3-rc2] Bluetooth: hci_uart: check for missing tty
 operations

On Thu, Aug 01, 2019 at 01:31:31PM +0000, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: .
> 
> The bot has tested the following trees: v5.2.4, v5.1.21, v4.19.62, v4.14.134, v4.9.186, v4.4.186.
> 
> v5.2.4: Build OK!
> v5.1.21: Build OK!
> v4.19.62: Build OK!
> v4.14.134: Failed to apply! Possible dependencies:
>     25a13e382de2 ("bluetooth: hci_qca: Replace GFP_ATOMIC with GFP_KERNEL")
> 
> v4.9.186: Failed to apply! Possible dependencies:
>     25a13e382de2 ("bluetooth: hci_qca: Replace GFP_ATOMIC with GFP_KERNEL")
> 
> v4.4.186: Failed to apply! Possible dependencies:
>     162f812f23ba ("Bluetooth: hci_uart: Add Marvell support")
>     25a13e382de2 ("bluetooth: hci_qca: Replace GFP_ATOMIC with GFP_KERNEL")
>     395174bb07c1 ("Bluetooth: hci_uart: Add Intel/AG6xx support")
>     9e69130c4efc ("Bluetooth: hci_uart: Add Nokia Protocol identifier")
> 
> 
> NOTE: The patch will not be queued to stable trees until it is upstream.
> 
> How should we proceed with this patch?

Already fixed up by hand and queued up, your automated email is a bit
slow :)

greg k-h