Hello! Assume a user-space application "A" calls poll to see if a write would block. ->The poll call then suceeds and the application "A" will now perform a "nonblocking write". Must this application's "nonblocking write" now succeed [-OR-] or is it allowed, that the instance in "ssize_t device_read()" returns -EAGAIN, so that the application must loop back and poll again. Consider what happens if the poll succeeds, but another application "B" is faster and performs the write before "A"! -> Must this be prevented according to Linux/Unix semantics, or is it the programmer's choice if he/she wishes to implement that lock??? Thanks -Albert -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
