From: Rainer Weikusat <rweikusat@mobileactivedefense•com>
To: David Miller <davem@davemloft•net>
Cc: eric.dumazet@gmail•com, David.Laight@ACULAB•COM, netdev@vger•kernel.org
Subject: Re: [PATCH] net: unix: non blocking recvmsg() should not return -EINTR
Date: Fri, 28 Mar 2014 20:35:34 +0000 [thread overview]
Message-ID: <87ob0q3vu1.fsf@sable.mobileactivedefense.com> (raw)
In-Reply-To: <87a9cc7j1o.fsf@sable.mobileactivedefense.com> (Rainer Weikusat's message of "Wed, 26 Mar 2014 21:21:23 +0000")
Rainer Weikusat <rw@sable> writes:
[...]
> ---------
> #include <fcntl.h>
> #include <string.h>
> #include <sys/socket.h>
> #include <sys/un.h>
>
> int main(void)
> {
> struct sockaddr_un sun;
> int fd;
>
> fd = socket(AF_UNIX, SOCK_DGRAM, 0);
> sun.sun_family = AF_UNIX;
> strncpy(sun.sun_path, "/tmp/bla", sizeof(sun.sun_path));
> bind(fd, (struct sockaddr *)&sun, sizeof(sun));
>
> if (fork() == 0) read(fd, &fd, sizeof(fd));
>
> sleep(1);
>
> fcntl(fd, F_SETFL, O_NONBLOCK);
> read(fd, &fd, sizeof(fd));
>
> return 0;
> }
> --------
In the interest of fairness, here's a more realistic test case (tested
on 3.2.9 and 3.2.54):
--------------
#include <fcntl.h>
#include <string.h>
#include <sys/socket.h>
#include <sys/un.h>
int main(void)
{
struct sockaddr_un sun;
int fd;
fd = socket(AF_UNIX, SOCK_DGRAM, 0);
sun.sun_family = AF_UNIX;
strncpy(sun.sun_path, "/tmp/bla", sizeof(sun.sun_path));
bind(fd, (struct sockaddr *)&sun, sizeof(sun));
if (fork() == 0) recv(fd, &fd, sizeof(fd), 0);
sleep(1);
recv(fd, &fd, sizeof(fd), MSG_DONTWAIT);
return 0;
}
prev parent reply other threads:[~2014-03-28 20:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 1:42 [PATCH] net: unix: non blocking recvmsg() should not return -EINTR Eric Dumazet
2014-03-26 13:17 ` Rainer Weikusat
2014-03-26 13:57 ` Rainer Weikusat
2014-03-26 14:09 ` Eric Dumazet
2014-03-26 14:25 ` Rainer Weikusat
2014-03-26 15:00 ` David Laight
2014-03-26 15:13 ` Rainer Weikusat
2014-03-26 15:25 ` Eric Dumazet
2014-03-26 15:33 ` Eric Dumazet
2014-03-26 19:46 ` Rainer Weikusat
2014-03-26 21:04 ` Rainer Weikusat
2014-03-27 9:36 ` David Laight
2014-03-27 12:40 ` Rainer Weikusat
2014-03-27 12:49 ` Jamal Hadi Salim
2014-03-27 13:02 ` Rainer Weikusat
2014-03-27 12:53 ` David Laight
2014-03-27 13:29 ` Rainer Weikusat
2014-03-26 21:05 ` David Miller
2014-03-26 21:21 ` Rainer Weikusat
2014-03-26 21:44 ` Eric Dumazet
2014-03-26 22:06 ` Rainer Weikusat
2014-03-26 22:35 ` Eric Dumazet
2014-03-26 22:51 ` Rainer Weikusat
2014-03-26 22:58 ` Eric Dumazet
2014-03-28 20:35 ` Rainer Weikusat [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ob0q3vu1.fsf@sable.mobileactivedefense.com \
--to=rweikusat@mobileactivedefense$(echo .)com \
--cc=David.Laight@ACULAB$(echo .)COM \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox