Segmentation fault in NFC binding

Description

I tried the NFC binding but had no chance to make it works.

I'm currently using a master image (head of the nfc binding repo: 557e5f0, so it's not the same segfault as the one fixed by the last commit), on a M3+Kingfisher and two different NFC reader.

When I use the reference reader (ACR122) as well as the fallback reader (SCL3711), I have the following log when I tap a tag:

Note that the first two lines appears only with some tags, but not all.

Also, with the reference reader (ACR122) it can take up to 10 seconds before a tag is detected.

Environment

None

Activity

Raquel Medina

January 24, 2019 at 8:51 PM

Merged to flounder under gerrit Change 19535.

Raquel Medina

January 14, 2019 at 8:52 AM

Fix was merged to master under gerrit Change 19483.

Cherry-picked to flounder under gerrit Change 19535, waiting for cdoe review.

Raquel Medina

January 4, 2019 at 5:27 PM

I found a random segfault on agl-service-nfc caused by memory corruption originated in libneardal.

On record memory release, a memset operation was done on the freed memory, providing a chance for corruption if the memory was claimed by other process before the memset.

Raquel Medina

December 15, 2018 at 10:34 PM

I have reproduced the issue by reading tags back to back. It happens after reading a number of times, usually over 10+ cycles, although it varies and it can take longer (20, 30 or even 50+) to reproduce.

I can reproduce at will now, and I'm investigating it.

Raquel Medina

December 4, 2018 at 2:01 PM

I havent been able to reproduce this issue usign empty NTAG213.

Resize work item view side panel

Fixed

Details

Assignee

Raquel Medina

Reporter

Loïc Collignon [ IoT.bzh ]

Priority

Major

Created November 26, 2018 at 2:33 PM

Updated February 12, 2019 at 1:50 AM

Resolved January 25, 2019 at 12:10 AM

Segmentation fault in NFC binding

Description

Environment

Activity

Details

Assignee

Reporter

Fix versions

Labels

Affects versions

Priority