From: Eric Dumazet <dada1@cosmosbay.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mingo@elte.hu, tglx@linutronix.de, torvalds@linux-foundation.org
Subject: Re: [PATCHv4 0/6] sys_indirect system call
Date: Tue, 20 Nov 2007 10:13:01 +0100 [thread overview]
Message-ID: <4742A51D.5080009@cosmosbay.com> (raw)
In-Reply-To: <200711200653.lAK6rEYP025876@devserv.devel.redhat.com>
Ulrich Drepper a écrit :
> wing patches provide an alternative implementation of the
> sys_indirect system call which has been discussed a few times.
> This no system call allows us to extend existing system call
> interfaces with adding more system calls.
I am wondering if some parts are missing from your ChangeLog
You apparently added in v3 a new 'flags' parameter to indirect syscall but no
trace of this change in Changelog, and why it was added. This seems to imply a
future multiplexor.
And no change in the test program reflecting this 'flags' new param, so it fails.
> fd = syscall (__NR_indirect, &r, &i, sizeof (i));
should be fd = syscall (__NR_indirect, &r, &i, sizeof (i), 0);
> int s2 = fcntl (fd, F_GETFD);
> int t2 = fcntl (fd, F_GETFL);
> printf ("new: FD_CLOEXEC %s set, NONBLOCK %s set\n",
> s2 == 0 ? "not" : "is", (t2 & O_NONBLOCK) ? "is" : "not");
> close (fd);
>
> i.file_flags.flags = O_CLOEXEC;
> sigset_t ss;
> sigemptyset(&ss);
> FILL_IN(r, __NR_signalfd, -1, (long) &ss, 8);
> fd = syscall (__NR_indirect, &r, &i, sizeof (i));
same here ?
> int s3 = fcntl (fd, F_GETFD);
> printf ("signalfd: FD_CLOEXEC %s set\n", s3 == 0 ? "not" : "is");
> close (fd);
>
> FILL_IN(r, __NR_eventfd, 8);
> fd = syscall (__NR_indirect, &r, &i, sizeof (i));
and here.
> int s4 = fcntl (fd, F_GETFD);
> printf ("eventfd: FD_CLOEXEC %s set\n", s4 == 0 ? "not" : "is");
> close (fd);
>
> return s1 != 0 || s2 == 0 || t1 != 0 || t2 == 0 || s3 == 0 || s4 == 0;
> }
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2007-11-20 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 6:53 [PATCHv4 0/6] sys_indirect system call Ulrich Drepper
2007-11-20 9:13 ` Eric Dumazet [this message]
2007-11-20 16:11 ` Ulrich Drepper
2007-11-20 18:08 ` Zach Brown
2007-11-20 18:17 ` Ulrich Drepper
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=4742A51D.5080009@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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