public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/12043] New: aio notification via signal doesn't handle sigqueue errors propertly
@ 2010-09-20 11:12 alkondratenko at gmail dot com
0 siblings, 0 replies; only message in thread
From: alkondratenko at gmail dot com @ 2010-09-20 11:12 UTC (permalink / raw)
To: glibc-bugs
When signal queue is full sigqueue will fail. When that happens no IO completion
notification will ever be delivered.
I suspect the designers of sigev_signal completion notification type envisioned
that aio_{read,write} should reserve place in signal queue at the start of IO
operation and return error if resource limits are reached. But glibc
implementation, obviously, cannot do that, because there is no way to
reserve/prepare/provision future sigqueue call.
--
Summary: aio notification via signal doesn't handle sigqueue
errors propertly
Product: glibc
Version: 2.13
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper dot fsp at gmail dot com
ReportedBy: alkondratenko at gmail dot com
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=12043
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-09-20 11:12 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-09-20 11:12 [Bug libc/12043] New: aio notification via signal doesn't handle sigqueue errors propertly alkondratenko at gmail dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).