This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/4465] New: pthread cancellation points missing for fdatasync and lockf in some cases
- From: "vapier at gentoo dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 6 May 2007 07:58:12 -0000
- Subject: [Bug nptl/4465] New: pthread cancellation points missing for fdatasync and lockf in some cases
- Reply-to: sourceware-bugzilla at sourceware dot org
POSIX requires fdatasync() and lockf() be pthread cancellation endpoints but it
looks like they get missed a little in glibc ...
fdatasync() is generated for Linux simply via syscalls.list as a pass through to
the kernel... the generic case in misc/fdatasync.c relies on fsync() being a
cancellation endpoint ... so here, just Linux is broken it seems
as for lockf(), this seems to be [incorrectly] done on purpose ... io/lockf.c
talks about relying on fcntl()'s cancellation endpoint when called with F_SETLKW
as that is the only case that POSIX says fcntl() should be a cancellation
endpoint ... however, POSIX does not grant this limitation to lockf() ... it
should always be a cancellation endpoint regardless of the arguments it is
called with
--
Summary: pthread cancellation points missing for fdatasync and
lockf in some cases
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: nptl
AssignedTo: drepper at redhat dot com
ReportedBy: vapier at gentoo dot org
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=4465
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.