fix history segfault following transport disconnect 85/25485/1 10.91.0 10.92.0 10.93.0 11.91.0 11.92.0 12.90.0 12.90.1 12.91.0 12.92.0 12.93.0 13.93.0 koi/10.91.0 koi/10.92.0 koi/10.93.0 koi_10.91.0 koi_10.92.0 koi_10.93.0 lamprey/11.91.0 lamprey/11.92.0 lamprey_11.91.0 lamprey_11.92.0 marlin/12.90.0 marlin/12.90.1 marlin/12.91.0 marlin/12.92.0 marlin/12.93.0 marlin_12.90.0 marlin_12.90.1 marlin_12.91.0 marlin_12.92.0 marlin_12.93.0 needlefish/13.93.0 needlefish_13.93.0
authorRaquel Medina <raquel.medina@konsulko.com>
Wed, 21 Oct 2020 11:20:34 +0000 (13:20 +0200)
committerRaquel Medina <raquel.medina@konsulko.com>
Mon, 26 Oct 2020 12:30:44 +0000 (13:30 +0100)
commitbdcd1fe42febb04e1be428bdfa022f89b65a1cb1
tree739091f4a4857d57b48e0a20fc6a6e7fc7bc5381
parent512c2dc6df87fff1fca05d791bb28a5b3faa2586
fix history segfault following transport disconnect

The segmentation fault manifests if the remote
disconnects pbap transport followed by a refresh
pbap data operation.
The root cause is a read operation of
vcard data for the calls history, ignoring the error
triggered while attempting to access the
corresponding file on the remote device.
The current patch introduces the missing check for
errors.

SPEC-3652
Signed-off-by: Raquel Medina <raquel.medina@konsulko.com>
Change-Id: I916ba5b8b5fc29aa9b928dbf2ed3e7c892d15891

test & deleteme

Signed-off-by: Raquel Medina <raquel.medina@konsulko.com>
Change-Id: I9efa151af54ae87cbf7e67bb6b985a76e0814549
binding/bluetooth-pbap-binding.c