Hi Johan, >>> so I am curious now to what happens if we are running SMP and at the >>> same time are doing RPA resolving. Can the same crypto context be used >>> that way? >> >> That's a fair point, and after a quick look through the crypto API it >> seems like this might not be safe. A simple fix would be to ensure that >> any access is between hci_dev_lock & hci_dev_unlock. > > A quick check shows that all access external to smp.c is already done > under the hdev lock but the two places internal to smp.c are not (both > of which are from within workqueue callbacks, so taking the lock there > should be safe). Do you agree that this is the simplest/best solution? since we always do only one AES round anyway, that seems to be a good solution to this. 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
