This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

pthread cancellation points missing for fdatasync and lockf in some cases


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
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]