diff options
| author | Nikita Ioffe <ioffe@google.com> | 2020-11-06 20:20:31 +0000 |
|---|---|---|
| committer | Nikita Ioffe <ioffe@google.com> | 2020-11-06 22:38:23 +0000 |
| commit | c2d4de2af0b6621a7afb9463542cb0abee76b8c2 (patch) | |
| tree | c36282135e1ab7e0b8c49f6e392db32e37b9bba3 /trusty/coverage/coverage.cpp | |
| parent | 4071463e2f5a62b323dd43ba7064d9109e40ac1d (diff) | |
Don't SIGABORT if device-mapper doesn't generate uevent for DeleteDevice
It looks like in some rare scenarios device-mapper won't create an
uevent while handling DM_DEV_REMOVE ioctl.
Since failure to generate uevent will result in ueventd not cleaning up
/dev paths in user space, it should be ok to just fail DeleteDevice call
without aborting the entire process.
Test: presubmit
Bug: 171266986
Change-Id: Iece28e6e02c35ac4bf33b9be74dfe1bbbb466bd4
Diffstat (limited to 'trusty/coverage/coverage.cpp')
0 files changed, 0 insertions, 0 deletions