Your message dated Wed, 11 Dec 2013 09:55:38 +0000 with message-id <[email protected]> and subject line Bug#731813: Removed package(s) from unstable has caused the Debian Bug report #693663, regarding pvcam: Several bugs that make it unready to release to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 693663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693663 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: pvcam-dkms Version: 4.1.0-2 Severity: grave There is a complete lack of locking, memory barriers or anything that could protect against races: - Two tasks calling device_open() on the same camera at the same time may race and succeed, which violates the assumption that: /* With the Linux driver - each camera */ /* is totally exclusive use! */ - Two tasks may race in device_ioctl() on the same file. - The ISR is not synchronised with the tasks requesting I/O. A failed device_ioctl() may mark the camera closed, but doesn't prevent the same file handle from being used, so again there can be two file handles for the same camera. Various functions can return positive numbers (= success) for errors. device_ioctl() doesn't consistently check whether copy_from_user() or copy_to_user() succeeded. pvcam_create_buffer() doesn't map memory correctly: virt_to_bus() doesn't generally work for PCI devices, and won't translate NULL to 0, so in case memory allocation fails it will not abort. pvcam_write_read() assumes little-endian byte order on the host. loadPCIflash() reads directly from user addresses without using copy_from_user(). Unimplemented functions quietly do nothing instead of returning a meaningful error. In most error cases that the driver actually bothers to check for, it immediately returns without clearing up resources that have been allocated. This can result in a crash or resource leak. Ben. -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pvcam-dkms depends on: ii dkms 2.2.0.3-1.2 Versions of packages pvcam-dkms recommends: pn libpvcam <none> pvcam-dkms suggests no packages.
--- End Message ---
--- Begin Message ---Version: 4.1.0-2+rm Dear submitter, as the package pvcam-dkms has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/731813 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Ansgar Burchardt (the ftpmaster behind the curtain)
--- End Message ---
