Date: Fri, 19 Jul 2002 23:46:25 +0200 (CEST) From: Juergen Weiss <weiss@uni-mainz.de> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/40792: signals lead to data loss on device ugen Message-ID: <200207192146.g6JLkPI5055845@zdvnetz.zdv.Uni-Mainz.DE>
next in thread | raw e-mail | index | archive | help
>Number: 40792 >Category: kern >Synopsis: signals lead to data loss on device ugen >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jul 19 14:50:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Juergen Weiss >Release: FreeBSD 4.6-RELEASE i386 >Organization: Universitaet Mainz >Environment: System: FreeBSD zdvnetz.zdv.Uni-Mainz.DE 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Fri Jun 21 17:02:57 CEST 2002 root@zdvnetz.zdv.Uni-Mainz.DE:/usr/src/sys/compile/MPEG i386 >Description: I used a usb smartcard reader. I accessed the device using ugen0.5 and ugen0.6 read/write calls. The protocol is request/response, that is write a command/data, read results. Originally the software was compiled with -ptread. Using the software lead to intermittent lockups. Using ktrace showed, that signals (SIGPROF) from the thread library led to lost data and lockup, that is after a command write, there where no data to be read. An inspection of the usb source code seems to indicate, that signals during read calls lead to loss of data in buffers. >How-To-Repeat: see above. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207192146.g6JLkPI5055845>