This is the mail archive of the glibc-bugs@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]

[Bug libc/12043] New: aio notification via signal doesn't handle sigqueue errors propertly


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.


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