Bug#684645: liblockfile1: Order of fcntl and dotlock in maillock

2012-10-31 Thread Michael Stapelberg
Hi paul, paul.sz...@sydney.edu.au writes: > I wonder if I am qualified to provide patches. What has me stumped > is that I do not seem to be able to build sendmail-bin. Trying: > > tar zxf sendmail.8.14.4.tar.gz > gzcat sendmail_8.14.4-2.1.diff.gz | patch -p0 > cd sendmail-8.14.4 > dpkg-bu

Bug#684645: liblockfile1: Order of fcntl and dotlock in maillock

2012-10-27 Thread paul . szabo
Dear Michael, I guess that lockmbox() should not be called on entry to deliver(), but that block moved to after the first flock(). I wonder about the close(mbfd) in line 1370: should unlockmbox() be called just after, and lockmbox() called again after the re-open and subsequent flock()? --- I w

Bug#684645: liblockfile1: Order of fcntl and dotlock in maillock

2012-10-26 Thread Michael Stapelberg
Hi Paul, On Sun, 12 Aug 2012 22:34:57 +1000 Paul Szabo wrote: > ... 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[100]. Us

Bug#684645: liblockfile1: Order of fcntl and dotlock in maillock

2012-08-12 Thread Paul Szabo
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 fcn