RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1348586 - pcscd killed by SIGSEV after reconnecting Smartcard
Summary: pcscd killed by SIGSEV after reconnecting Smartcard
Keywords:
Status: CLOSED DUPLICATE of bug 1286320
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcsc-lite
Version: 7.4
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Bob Relyea
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-21 13:50 UTC by Radek Duda
Modified: 2017-03-21 19:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-21 19:03:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
backtrace (8.87 KB, text/plain)
2016-06-21 13:50 UTC, Radek Duda
no flags Details

Description Radek Duda 2016-06-21 13:50:37 UTC
Created attachment 1170291 [details]
backtrace

Description of problem:
After reconnecting Smartcard, the pcscd is killed by SIGSEV

Version-Release number of selected component (if applicable):
rhel 7.3 nightly
pcsc-lite-1.8.8-6.el7.x86_64

How reproducible:always


Steps to Reproduce:
1.reconnect smartcard
2.
3.

Actual results:pcscd is killed by SIGSEV


Expected results:pcscd survives


Additional info:
Before connecting smartcard back, the cpu load increases massively as reported in bug 1286320. Besides pcscd CPU load of gnome-settings-deamon is increased as well (to cca 60% both).

Comment 2 Bob Relyea 2016-06-29 22:31:19 UTC
Please describe the issue more clearly. Do you mean 'programatically reconnect to the smart card' or do you mean reinserting the smart card. If the latter a code fragment would be preferable.

I'm currently running pcsc-lite-1.8.8-6.el7.x86_64
on my system and I'm able to access and use the smart card without load issues or crashing pcsc-lite.

Also, what pkcs #11 module are you using to access the smart card?

bob

Comment 3 Radek Duda 2016-06-30 07:28:04 UTC
Yes I see it is not clear enought.I mean unplugging USB connector of smartcard reader from computer and then plugging it back. It does not matter if a smartcard is inserted into reader or not during replugging. SIGSEGV is always there. IMHO this bug is dependent on bug 1286320.

I am using on my system (rhel7.3 nightly):
pcsc-lite-libs-1.8.8-6.el7.x86_64
pcsc-lite-1.8.8-6.el7.x86_64
pcsc-lite-ccid-1.4.10-11.el7.x86_64
coolkey-1.1.0-34.el7.x86_64
pam_pkcs11-0.6.2-24.el7.x86_64
kernel-3.10.0-455.el7.x86_64

so I am using CoolKey PKCS #11 Module and Gemalto Pc Twin Smart Card Reader. 

I am adding gdb backtrace (not from abrt) here:

(gdb) c
Continuing.
[Thread 0x7f820f8c2700 (LWP 20353) exited] <-  unplugged the SmartCard reader here

Program received signal SIGSEGV, Segmentation fault. <- plugged SmartCard reader here
[Switching to Thread 0x7f82100c3700 (LWP 20352)]
0x00007f82100d382c in ?? ()
(gdb) t a a bt

Thread 5 (Thread 0x7f82100c3700 (LWP 20352)):
#0  0x00007f82100d382c in ?? ()
#1  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f820f0c1700 (LWP 20354)):
#0  0x00007f82119b2b53 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f82124de283 in HPEstablishUSBNotifications (udev=0x7f8213d8bf00) at hotplug_libudev.c:570
#2  0x00007f8211c8cdc5 in start_thread (arg=0x7f820f0c1700) at pthread_create.c:308
#3  0x00007f82119bb6ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7f820e8c0700 (LWP 20397)):
#0  0x00007f82119b2b53 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f82124e0af1 in MessageReceive (buffer_void=buffer_void@entry=0x7f820e89fd30, buffer_size=buffer_size@entry=8, filedes=filedes@entry=12) at winscard_msg.c:442
#2  0x00007f82124e183f in ContextThread (newContext=0x7f8213da6ab0) at winscard_svc.c:304
#3  0x00007f8211c8cdc5 in start_thread (arg=0x7f820e8c0700) at pthread_create.c:308
#4  0x00007f82119bb6ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f8212494740 (LWP 20351)):
#0  0x00007f82119b2b53 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f82124e0e77 in ProcessEventsServer (pdwClientID=pdwClientID@entry=0x7ffe47bbe90c) at winscard_msg_srv.c:202
#2  0x00007f82124d2ae5 in SVCServiceRunLoop () at pcscdaemon.c:89
#3  main (argc=3, argv=<optimized out>) at pcscdaemon.c:630

Comment 4 Bob Relyea 2016-07-01 21:11:53 UTC
OK, this sound like the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1286320

I'll keep it open for RHEL 7.4 in case the it' not. If you can test the coolkey build to see if it fixes your issue if it does, go ahead and close it. I wasn't seeing a crash, but I was seeing pcsc-lite got to max CPU with I did this on my machine.

Comment 5 Bob Relyea 2017-03-20 23:56:34 UTC
does updating to coolkey-1.1.0-35.el7 fix your problem? see comment 4

Comment 6 Radek Duda 2017-03-21 08:48:02 UTC
(In reply to Bob Relyea from comment #5)
> does updating to coolkey-1.1.0-35.el7 fix your problem? see comment 4

Yes it solves the problem.

Comment 7 Bob Relyea 2017-03-21 19:03:40 UTC
Thanks Radek, closing as a duplication of bug 1286320

*** This bug has been marked as a duplicate of bug 1286320 ***


Note You need to log in before you can comment on or make changes to this bug.