Re: [RFC PATCH v1 2/2] Bluetooth: queue L2CAP conn req if encryption is needed

Hi Luiz, > It is possible to receive an L2CAP conn req for an encrypted > connection, before actually receiving the HCI change encryption > event. If this happened, the received L2CAP packet will be ignored. >>> >>> How is this possible? Or you are referring to a race between the ACL

Re: [RFC PATCH v1 2/2] Bluetooth: queue L2CAP conn req if encryption is needed

Hi Marcel, On Mon, Jun 29, 2020 at 1:21 PM Marcel Holtmann wrote: > > Hi Luiz, > > >>> It is possible to receive an L2CAP conn req for an encrypted > >>> connection, before actually receiving the HCI change encryption > >>> event. If this happened, the received L2CAP packet will be ignored. > > >

Re: [RFC PATCH v1 2/2] Bluetooth: queue L2CAP conn req if encryption is needed

Hi Archie, > It is possible to receive an L2CAP conn req for an encrypted > connection, before actually receiving the HCI change encryption > event. If this happened, the received L2CAP packet will be ignored. > > This patch queues the L2CAP packet and process them after the > expected HCI event

Re: [RFC PATCH v1 2/2] Bluetooth: queue L2CAP conn req if encryption is needed

Hi Luiz, >>> It is possible to receive an L2CAP conn req for an encrypted >>> connection, before actually receiving the HCI change encryption >>> event. If this happened, the received L2CAP packet will be ignored. > > How is this possible? Or you are referring to a race between the ACL > and Even

Re: [RFC PATCH v1 2/2] Bluetooth: queue L2CAP conn req if encryption is needed

Hi Marcel, Archie, On Mon, Jun 29, 2020 at 12:00 PM Marcel Holtmann wrote: > > Hi Archie, > > > It is possible to receive an L2CAP conn req for an encrypted > > connection, before actually receiving the HCI change encryption > > event. If this happened, the received L2CAP packet will be ignored.