| commit | 3b39a9ef6a0015a2d7a55910e42739314c291487 | [log] [tgz] |
|---|---|---|
| author | Nikita Ioffe <ioffe@google.com> | Fri Nov 06 20:20:31 2020 +0000 |
| committer | Nikita Ioffe <ioffe@google.com> | Fri Nov 06 22:38:23 2020 +0000 |
| tree | c36282135e1ab7e0b8c49f6e392db32e37b9bba3 | |
| parent | f7c47f81bae57531d23cdae551376c0c14636e0d [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