| 2016-03-01 18:22:30 |
Casey Marshall |
bug |
|
|
added bug |
| 2016-03-01 19:38:04 |
Ludovic Rousseau |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812087 |
|
| 2016-03-03 04:12:14 |
Casey Marshall |
attachment added |
|
pcscd debug output (redacted) https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4587143/+files/pcscd.log.redacted |
|
| 2016-03-04 18:23:47 |
Casey Marshall |
attachment added |
|
pcscd binary and core dump https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4588518/+files/pcscd-core-bin.tgz |
|
| 2016-03-04 18:25:49 |
Casey Marshall |
attachment removed |
pcscd binary and core dump https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4588518/+files/pcscd-core-bin.tgz |
|
|
| 2016-03-04 18:26:18 |
Casey Marshall |
attachment added |
|
pcscd binary and core dump https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4588521/+files/pcscd-core-bin.tar.bz2 |
|
| 2016-03-24 17:26:46 |
Launchpad Janitor |
pcsc-lite (Ubuntu): status |
New |
Confirmed |
|
| 2016-03-29 08:03:09 |
Johnny Izzo |
attachment added |
|
lsusb-v.txt https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4615641/+files/lsusb-v.txt |
|
| 2016-04-19 07:51:40 |
Ludovic Rousseau |
bug task added |
|
pcsc-lite (Debian) |
|
| 2016-04-19 14:59:38 |
Bug Watch Updater |
pcsc-lite (Debian): status |
Unknown |
Confirmed |
|
| 2016-04-20 15:48:19 |
Bug Watch Updater |
pcsc-lite (Debian): status |
Confirmed |
Fix Released |
|
| 2016-05-09 20:23:31 |
Evan Broder |
bug task added |
|
ccid (Ubuntu) |
|
| 2016-05-09 20:23:59 |
Evan Broder |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-05-09 20:23:59 |
Evan Broder |
bug task added |
|
ccid (Ubuntu Xenial) |
|
| 2016-05-09 20:23:59 |
Evan Broder |
bug task added |
|
pcsc-lite (Ubuntu Xenial) |
|
| 2016-05-09 20:24:11 |
Evan Broder |
ccid (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2016-05-09 20:24:14 |
Evan Broder |
ccid (Ubuntu): status |
New |
Fix Released |
|
| 2016-05-09 20:24:18 |
Evan Broder |
pcsc-lite (Ubuntu): status |
Confirmed |
Invalid |
|
| 2016-05-09 20:24:21 |
Evan Broder |
pcsc-lite (Ubuntu Xenial): status |
New |
Invalid |
|
| 2016-05-09 20:32:46 |
Evan Broder |
attachment added |
|
ccid_1.4.22-1ubuntu0.1.debdiff https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1551897/+attachment/4659458/+files/ccid_1.4.22-1ubuntu0.1.debdiff |
|
| 2016-05-09 20:46:45 |
Evan Broder |
description |
In xenial, pcscd CPU utilization occasionally goes haywire:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit
I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again.
Never had this issue on same hardware incl. smartcard with trusty.
I wonder if it might be this? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718473 |
[DESCRIPTION]
When hotplugging a composite USB device that expose multiple interfaces (such as a Yubikey NEO or Yubikey 4), libccid does not correctly de-initialize the USB library when it skips over the non-CCID interface.
This subsequently results in pcscd (or, presumably, anything that loads libccid, though I don't think anything else does) either using 100% CPU or segfaulting when the device is unplugged.
This seems worthy of an SRU as it is an easily reproducible bug with a simple, targeted fix.
[TEST CASE]
1. Make sure pcscd is running (sudo systemctl start pcscd; possibly sudo systemctl restart pcscd if a potentially fixed package has just been installed)
2. Plug and then unplug a composite USB device that includes a CCID interface (such as a Yubikey NEO)
3. Observe that pcscd has crashed with a segfault (sudo systemctl status pcscd)
[REGRESSION POTENTIAL]
The patch is quite narrow, and thus the potential for regression should be limited. The new code adds calls to close_libusb_if_needed, which is already written to be fairly conservative.
The worst case here is likely an unexpected call to libusb_exit, which could cause libusb to get into an inconsistent state. However, in practice the call seems quite safe, and the likelihood of regression low.
======
Original bug description:
In xenial, pcscd CPU utilization occasionally goes haywire:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit
I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again.
Never had this issue on same hardware incl. smartcard with trusty.
I wonder if it might be this? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718473 |
|
| 2016-05-09 20:47:23 |
Evan Broder |
description |
[DESCRIPTION]
When hotplugging a composite USB device that expose multiple interfaces (such as a Yubikey NEO or Yubikey 4), libccid does not correctly de-initialize the USB library when it skips over the non-CCID interface.
This subsequently results in pcscd (or, presumably, anything that loads libccid, though I don't think anything else does) either using 100% CPU or segfaulting when the device is unplugged.
This seems worthy of an SRU as it is an easily reproducible bug with a simple, targeted fix.
[TEST CASE]
1. Make sure pcscd is running (sudo systemctl start pcscd; possibly sudo systemctl restart pcscd if a potentially fixed package has just been installed)
2. Plug and then unplug a composite USB device that includes a CCID interface (such as a Yubikey NEO)
3. Observe that pcscd has crashed with a segfault (sudo systemctl status pcscd)
[REGRESSION POTENTIAL]
The patch is quite narrow, and thus the potential for regression should be limited. The new code adds calls to close_libusb_if_needed, which is already written to be fairly conservative.
The worst case here is likely an unexpected call to libusb_exit, which could cause libusb to get into an inconsistent state. However, in practice the call seems quite safe, and the likelihood of regression low.
======
Original bug description:
In xenial, pcscd CPU utilization occasionally goes haywire:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit
I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again.
Never had this issue on same hardware incl. smartcard with trusty.
I wonder if it might be this? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718473 |
[Impact]
When hotplugging a composite USB device that expose multiple interfaces (such as a Yubikey NEO or Yubikey 4), libccid does not correctly de-initialize the USB library when it skips over the non-CCID interface.
This subsequently results in pcscd (or, presumably, anything that loads libccid, though I don't think anything else does) either using 100% CPU or segfaulting when the device is unplugged.
This seems worthy of an SRU as it is an easily reproducible bug with a simple, targeted fix.
[Test Case]
1. Make sure pcscd is running (sudo systemctl start pcscd; possibly sudo systemctl restart pcscd if a potentially fixed package has just been installed)
2. Plug and then unplug a composite USB device that includes a CCID interface (such as a Yubikey NEO)
3. Observe that pcscd has crashed with a segfault (sudo systemctl status pcscd)
[Regression Potential]
The patch is quite narrow, and thus the potential for regression should be limited. The new code adds calls to close_libusb_if_needed, which is already written to be fairly conservative.
The worst case here is likely an unexpected call to libusb_exit, which could cause libusb to get into an inconsistent state. However, in practice the call seems quite safe, and the likelihood of regression low.
======
Original bug description:
In xenial, pcscd CPU utilization occasionally goes haywire:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit
I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again.
Never had this issue on same hardware incl. smartcard with trusty.
I wonder if it might be this? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718473 |
|
| 2016-05-09 20:54:41 |
Evan Broder |
ccid (Ubuntu Xenial): status |
Confirmed |
In Progress |
|
| 2016-05-18 08:31:13 |
Martin Pitt |
ccid (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-05-18 08:31:15 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-05-18 08:31:20 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2016-05-18 08:31:29 |
Martin Pitt |
tags |
|
verification-needed |
|
| 2016-05-18 22:17:22 |
Evan Broder |
bug |
|
|
added subscriber Evan Broder |
| 2016-05-18 22:19:56 |
Evan Broder |
tags |
verification-needed |
verification-done |
|
| 2016-05-25 13:04:29 |
Launchpad Janitor |
ccid (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-05-25 13:04:35 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
