Re: [PATCH] drivers/bluetooth/hci_ldisc.c: fix possible NULL dereferences

Hi Marcel, Marcel Holtmann wrote: Commit 22ad42033b7d2b3d7928fba9f89d1c7f8a3c9581 did not completely fix all the possible NULL dereferences. Besides hci_uart_close(), we also need to make sure that hdev is valid before calling hci_{unregister,free}_dev(). >>> I don't see any

Re: [PATCH] drivers/bluetooth/hci_ldisc.c: fix possible NULL dereferences

Hi Eugene, > >> Commit 22ad42033b7d2b3d7928fba9f89d1c7f8a3c9581 did not completely fix all > >> the possible NULL dereferences. Besides hci_uart_close(), we also need to > >> make sure that hdev is valid before calling hci_{unregister,free}_dev(). > > > > I don't see any issue. Without

Re: [PATCH] drivers/bluetooth/hci_ldisc.c: fix possible NULL dereferences

Hi Eugene, Commit 22ad42033b7d2b3d7928fba9f89d1c7f8a3c9581 did not completely fix all the possible NULL dereferences. Besides hci_uart_close(), we also need to make sure that hdev is valid before calling hci_{unregister,free}_dev(). I don't see any issue. Without HCI_UART_PROTO_SET,

Re: [PATCH] drivers/bluetooth/hci_ldisc.c: fix possible NULL dereferences

Hi Marcel, Marcel Holtmann wrote: Commit 22ad42033b7d2b3d7928fba9f89d1c7f8a3c9581 did not completely fix all the possible NULL dereferences. Besides hci_uart_close(), we also need to make sure that hdev is valid before calling hci_{unregister,free}_dev(). I don't see any issue. Without

Re: [PATCH] drivers/bluetooth/hci_ldisc.c: fix possible NULL dereferences

Hi Marcel, Marcel Holtmann wrote: >> Commit 22ad42033b7d2b3d7928fba9f89d1c7f8a3c9581 did not completely fix all >> the possible NULL dereferences. Besides hci_uart_close(), we also need to >> make sure that hdev is valid before calling hci_{unregister,free}_dev(). > > I don't see any issue.

Re: [PATCH] drivers/bluetooth/hci_ldisc.c: fix possible NULL dereferences

Hi Eugene, > Commit 22ad42033b7d2b3d7928fba9f89d1c7f8a3c9581 did not completely fix all > the possible NULL dereferences. Besides hci_uart_close(), we also need to > make sure that hdev is valid before calling hci_{unregister,free}_dev(). I don't see any issue. Without HCI_UART_PROTO_SET, the

[PATCH] drivers/bluetooth/hci_ldisc.c: fix possible NULL dereferences

Commit 22ad42033b7d2b3d7928fba9f89d1c7f8a3c9581 did not completely fix all the possible NULL dereferences. Besides hci_uart_close(), we also need to make sure that hdev is valid before calling hci_{unregister,free}_dev(). Signed-off-by: Eugene Teo <[EMAIL PROTECTED]> ---

[PATCH] drivers/bluetooth/hci_ldisc.c: fix possible NULL dereferences

Commit 22ad42033b7d2b3d7928fba9f89d1c7f8a3c9581 did not completely fix all the possible NULL dereferences. Besides hci_uart_close(), we also need to make sure that hdev is valid before calling hci_{unregister,free}_dev(). Signed-off-by: Eugene Teo [EMAIL PROTECTED] ---

Re: [PATCH] drivers/bluetooth/hci_ldisc.c: fix possible NULL dereferences

Hi Eugene, Commit 22ad42033b7d2b3d7928fba9f89d1c7f8a3c9581 did not completely fix all the possible NULL dereferences. Besides hci_uart_close(), we also need to make sure that hdev is valid before calling hci_{unregister,free}_dev(). I don't see any issue. Without HCI_UART_PROTO_SET, the

Re: [PATCH] drivers/bluetooth/hci_ldisc.c: fix possible NULL dereferences

Hi Marcel, Marcel Holtmann wrote: Commit 22ad42033b7d2b3d7928fba9f89d1c7f8a3c9581 did not completely fix all the possible NULL dereferences. Besides hci_uart_close(), we also need to make sure that hdev is valid before calling hci_{unregister,free}_dev(). I don't see any issue. Without