Package: liblockfile1 Version: 1.09-4 Severity: serious Justification: Policy 11.6
Debian policy http://www.debian.org/doc/debian-policy/ch-customized-programs.html#s-mail-transport-agents says: ... fcntl() locking must be combined with dot locking. To avoid deadlocks, a program should use fcntl() first and dot locking after this, or alternatively implement the two locking methods in a non blocking way. Using the functions maillock and mailunlock provided by the liblockfile* packages is the recommended way to realize this. Looking at an strace of /usr/lib/sm.bin/mail.local it seems to use /usr/lib/i386-linux-gnu/liblockfile.so.1 and shows: link("/var/mail/.lk10336dp639", "/var/mail/psz.lock") = 0 open("/var/mail/psz", O_WRONLY|O_APPEND) = 4 fcntl64(4, F_SETLKW, {type=F_WRLCK, whence=SEEK_CUR, start=0, len=0}) = 0 which seems the wrong order. Please see http://bugs.debian.org/648941 also. Thanks, Paul Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of Sydney Australia -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.21-pk06.02-i386 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages liblockfile1 depends on: ii libc6 2.13-33 ii liblockfile-bin 1.09-4 ii multiarch-support 2.13-33 liblockfile1 recommends no packages. liblockfile1 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
