Your message dated Sun, 11 Dec 2005 07:47:14 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#339037: fixed in manpages 2.14-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 14 Nov 2005 16:56:37 +0000
>From [EMAIL PROTECTED] Mon Nov 14 08:56:37 2005
Return-path: <[EMAIL PROTECTED]>
Received: from ptr-64-201-187-87.ptr.terago.ca ([64.201.187.87]
helo=mars.net-itech.com)
by spohr.debian.org with smtp (Exim 4.50)
id 1EbhdE-0005mg-T6
for [EMAIL PROTECTED]; Mon, 14 Nov 2005 08:56:37 -0800
Received: (qmail 7198 invoked from network); 14 Nov 2005 16:56:33 -0000
Received: from unknown (HELO insight.internal.nit.ca) (192.168.12.100)
by mars.net-itech.com with SMTP; 14 Nov 2005 16:56:33 -0000
Received: from apenwarr by insight.internal.nit.ca with local (Exim 3.34 #1
(Debian))
id 1EbhdA-0006Ff-00; Mon, 14 Nov 2005 11:56:32 -0500
Date: Mon, 14 Nov 2005 11:56:32 -0500
From: Avery Pennarun <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: open(2) man page doesn't document potential EWOULDBLOCK return code
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.5 required=4.0 tests=BAYES_10,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: manpages-dev
Version: 1.60-2
We've just been bitten by this at work.
If you read the LEASES section of fcntl(2), it explains that open() with
O_NONBLOCK could cause open to return EWOULDBLOCK. This is not explained
anywhere on the open() page; open() has many possible return codes, none of
which are EWOULDBLOCK. (There is a comment about opening fifos in
nonblocking mode, but the error code description implies that this would
return ENXIO, not EWOULDBLOCK.)
Also, the fcntl(2) page doesn't say whether opening a leased file with
O_NONBLOCK will actually request the lease to be broken or not. It appears
you *have* to open in blocking mode in order to open a leased file at all,
but that's not clear from the description.
It wouldn't be so bad to open in blocking mode since a lease is guaranteed
to be broken after a certain timeout. But a naive implementation would
introduce a security hole since the file might be replaced by surprise with
a FIFO, which has no open timeout at all.
Have fun,
Avery
---------------------------------------
Received: (at 339037-close) by bugs.debian.org; 11 Dec 2005 15:51:12 +0000
>From [EMAIL PROTECTED] Sun Dec 11 07:51:12 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1ElTPu-00025y-8f; Sun, 11 Dec 2005 07:47:14 -0800
From: Martin Schulze <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.60 $
Subject: Bug#339037: fixed in manpages 2.14-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sun, 11 Dec 2005 07:47:14 -0800
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Source: manpages
Source-Version: 2.14-1
We believe that the bug you reported is fixed in the latest version of
manpages, which is due to be installed in the Debian FTP archive:
manpages-dev_2.14-1_all.deb
to pool/main/m/manpages/manpages-dev_2.14-1_all.deb
manpages_2.14-1.diff.gz
to pool/main/m/manpages/manpages_2.14-1.diff.gz
manpages_2.14-1.dsc
to pool/main/m/manpages/manpages_2.14-1.dsc
manpages_2.14-1_all.deb
to pool/main/m/manpages/manpages_2.14-1_all.deb
manpages_2.14.orig.tar.gz
to pool/main/m/manpages/manpages_2.14.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin Schulze <[EMAIL PROTECTED]> (supplier of updated manpages package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sun, 11 Dec 2005 15:41:22 +0100
Source: manpages
Binary: manpages manpages-dev
Architecture: source all
Version: 2.14-1
Distribution: unstable
Urgency: low
Maintainer: Martin Schulze <[EMAIL PROTECTED]>
Changed-By: Martin Schulze <[EMAIL PROTECTED]>
Description:
manpages - Manual pages about using a GNU/Linux system
manpages-dev - Manual pages about using GNU/Linux for development
Closes: 336875 339037 339037
Changes:
manpages (2.14-1) unstable; urgency=low
.
* New upstream release, with the following changes
- New rexec(3) (Closes: Bug#336875)
- Clarified file leases in fcntl(2) (Closes: Bug#339037)
- Completed errors section in open(2) (Closes: Bug#339037)
Files:
3eec346638bba39f0d93d1114239d3c5 584 doc - manpages_2.14-1.dsc
dddd6cb167c71096b0a8164191f0fa22 1065989 doc - manpages_2.14.orig.tar.gz
600eb16e8b6f51db4fc7c801a306f068 47285 doc - manpages_2.14-1.diff.gz
ffb4681f1fd8dbd5d5cae40320a8adc6 406402 doc important manpages_2.14-1_all.deb
a7b32f93d360c41f706c3fd9c5190a36 1109608 doc standard
manpages-dev_2.14-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDnEbDW5ql+IAeqTIRAlT1AKCWuSmHU4LOlSHzh+u3E3UrTm0KZQCfVLTr
JQeF4sFsPwgn1/9qSwmIa5Q=
=I5zY
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
