Bug 1071243

Summary: [abrt] pcsc-lite: ausb_close(): pcscd killed by SIGABRT
Product: [Fedora] Fedora Reporter: Patrick Uiterwijk <puiterwijk>
Component: pcsc-liteAssignee: Nikos Mavrogiannopoulos <nmavrogi>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: kalevlember, ludovic.rousseau+fedoraproject, nmavrogi, puiterwijk, rrelyea, systemd-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2aeeb67f3eadb0e645c64bc89f497d79d64ac780
Whiteboard: abrt_hash:82969d11c2fc6ed2fe98f1bd82fa0615d5c187ed
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 01:27:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Patrick Uiterwijk 2014-02-28 11:01:59 UTC
Version-Release number of selected component:
pcsc-lite-1.8.10-1.fc20

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/sbin/pcscd --foreground --auto-exit
crash_function: ausb_close
executable:     /usr/sbin/pcscd
kernel:         3.12.10-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #5 ausb_close at ausb.c:178
 #6 CUSBUnix::Close at USBUnix.cpp:395
 #7 CUSBUnix::~CUSBUnix at USBUnix.cpp:161
 #9 CReader::Disonnect at Reader.cpp:186
 #10 IFDHandler::closeChannel at ifd.cpp:639
 #11 IFDHCloseChannel at ifd.cpp:1502
 #12 IFDCloseIFD at ifdwrapper.c:169
 #13 RFUnInitializeReader at readerfactory.c:1044
 #14 removeReader at readerfactory.c:559
 #15 _UnrefReader at readerfactory.c:104

Potential duplicate: bug 888192

Comment 1 Patrick Uiterwijk 2014-02-28 11:02:04 UTC
Created attachment 868976 [details]
File: backtrace

Comment 2 Patrick Uiterwijk 2014-02-28 11:02:07 UTC
Created attachment 868977 [details]
File: cgroup

Comment 3 Patrick Uiterwijk 2014-02-28 11:02:10 UTC
Created attachment 868978 [details]
File: core_backtrace

Comment 4 Patrick Uiterwijk 2014-02-28 11:02:13 UTC
Created attachment 868979 [details]
File: dso_list

Comment 5 Patrick Uiterwijk 2014-02-28 11:02:17 UTC
Created attachment 868980 [details]
File: environ

Comment 6 Patrick Uiterwijk 2014-02-28 11:02:19 UTC
Created attachment 868981 [details]
File: limits

Comment 7 Patrick Uiterwijk 2014-02-28 11:02:22 UTC
Created attachment 868982 [details]
File: maps

Comment 8 Patrick Uiterwijk 2014-02-28 11:02:24 UTC
Created attachment 868983 [details]
File: open_fds

Comment 9 Patrick Uiterwijk 2014-02-28 11:02:28 UTC
Created attachment 868984 [details]
File: proc_pid_status

Comment 10 Patrick Uiterwijk 2014-02-28 11:02:30 UTC
Created attachment 868985 [details]
File: var_log_messages

Comment 11 Nikos Mavrogiannopoulos 2014-06-03 08:08:46 UTC
The interesting parts in the backtrace are:

#0  0x00007f7af2d34703 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x000000000040e8fb in HPEstablishUSBNotifications (udev=0x1526e30) at 
        fd = -514
        udev_monitor = 0x7f7ae40008c0

Thus the crash in select occurred due to a negative file descriptor, and this (negative) fd was provided by udev_monitor_get_fd().

There is some issue in udev that caused the fd to be negative. Seeing its code it seems to return -EINVAL if udev_monitor == NULL, but this is not the case here.

I'll update the package with a sanity check for the file descriptor but that would only prevent the crash.

Some input from the libudev maintainer on why udev_monitor_get_fd() would return -514 may help clarify the issue.

Comment 12 Fedora Update System 2014-06-03 08:37:04 UTC
pcsc-lite-1.8.10-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/pcsc-lite-1.8.10-2.fc20

Comment 13 Nikos Mavrogiannopoulos 2014-06-05 09:23:37 UTC
Please provide feedback on whether the new release addresses your issue.

Comment 14 Fedora Update System 2014-07-23 03:01:47 UTC
pcsc-lite-1.8.10-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 15 Fedora End Of Life 2015-05-29 11:05:44 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 16 Fedora End Of Life 2015-06-30 01:27:12 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.