Writing a test for this case is non-trivial. IoTivity has the problem that two instances of it can't exist in the same process space, because of the use of global variables, for one thing. And we need to have two instances running and talking to each other to test these scenarios. We started looking into building some kind of test harness to have separate process spaces, but it's not a non-trivial undertaking. And that makes adding a regression test for this case also a non-trivial undertaking.
-----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Mats Wichmann Sent: Friday, April 21, 2017 4:44 PM To: Heldt-Sheller, Nathan <nathan.heldt-sheller at intel.com>; iotivity-dev at lists.iotivity.org Subject: Re: [dev] apparent deadlock in GetCASecureEndpointInfo()... known issue in 1.3-rel? On 04/21/2017 04:09 PM, Heldt-Sheller, Nathan wrote: > Hi again IoTivity devs, > > I opened a JIRA ticket > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjira.iotivity.org%2Fbrowse%2FIOT-2101&data=02%7C01%7Ckkane%40microsoft.com%7C17a96410f12f4ad3910708d4891042f4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636284150326913482&sdata=jcZPkosyShpo6L5nht%2BD%2BJzLxgOkQCSsxoZpfYAE%2F%2FE%3D&reserved=0 > and attached a log that shows that CAdecryptSsl() has the mutex, and then > GetCASecureEndpointData() is called and tries to get the mutex before > CAdecryptSsl() releases it. I'm not sure which changeset introduces this > problem and it's difficult to backtrack because the discovery step (which is > required in order to launch the onboarding step, where this deadlock occurs) > is broken in many prior commits, all the way back to when this deadlock > doesn't occur. > > Thanks in advance to anyone who has time to take a look at this. I've got to > get back to wrapping up OCF 1.0 changes for 1.3-rel. I'll keep working > around this issue as much as I can, but it's blocking at least one critical > changeset for 1.3-rel. > > Thanks, > Nathan > > From: iotivity-dev-bounces at lists.iotivity.org > [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf Of > Heldt-Sheller, Nathan > Sent: Friday, April 21, 2017 11:26 AM > To: iotivity-dev at lists.iotivity.org > Subject: [dev] apparent deadlock in GetCASecureEndpointInfo()... known issue > in 1.3-rel? > > Hi folks, > > I'm blocked in verifying some of my changes because the "provisioningclient" > apps seems to no longer work on 1.3-rel > (72e1ab0da3a9ce08e5423b64cb793b3b57493587). Discovery of the unowned device > works, but when I try to do JustWorks owner transfer I get: The hope would be when this gets fixed, there can also be a regression test written that catches any future breakage in this area. Though we've already seen some hint that the jenkins unit tests don't actually force secure mode, which needs investigation... _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev&data=02%7C01%7Ckkane%40microsoft.com%7C17a96410f12f4ad3910708d4891042f4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636284150326913482&sdata=7kMiMTeNT%2Fp2ciyxRNfHOTX6A8OvbqOJASIFJRlyG2E%3D&reserved=0
