Hi Johan, > We need to ensure that we do not send events to user space with the > identity address if we have not yet notified user space of the IRK. The > code was previously trying to handle this for the mgmt_pair_device > response (which worked well enough) but this is not the only connection > related event that might be sent to user space before pairing is > successful: another important event is Device Disconnected. > > The issue can actually be solved more simply than the solution > previously used for mgmt_pair_device. Since we do have the identity > address tracked as part of the remote IRK struct we can just copy it > over from there to the hci_conn struct once we've for real sent the mgmt > event for the new IRK. > > Signed-off-by: Johan Hedberg <johan.hedberg@xxxxxxxxx> > --- > v2: Move l2cap_conn_update_id_addr to the right place > > net/bluetooth/mgmt.c | 16 ++-------------- > net/bluetooth/smp.c | 16 +++++++++------- > 2 files changed, 11 insertions(+), 21 deletions(-) patch has been applied to bluetooth-next tree. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
