From: "Michael Kerrisk" <mtk.manpages@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "David Miller" <davem@davemloft.net>,
torvalds@linux-foundation.org, drepper@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
"akpm@linux-foundation.org Jakub Jelinek" <jakub@redhat.com>
Subject: Re: [PATCH] alternative to sys_indirect, part 1
Date: Thu, 24 Apr 2008 18:48:37 +0200 [thread overview]
Message-ID: <517f3f820804240948u788745f4s7a5dd4e7417ffeaf@mail.gmail.com> (raw)
In-Reply-To: <20080424164226.415cedeb@the-village.bc.nu>
On 4/24/08, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > But this approach fixes just one of the interfaces. There are 7 or 8
> > other interfaces that need to solve the same problem. What about
> > those?
>
>
> Actually it seems to fix most of them.
Am I missingg something? How? There a number of system calls that
have neither a flags argument, nor another argument that we can
overload (as you propose with socket()). For those, we'd need new
system calls os sys_indirect().
> I accept Jakub's observation we
> need a "paccept()" or similar.
True, that would be nice.
next prev parent reply other threads:[~2008-04-24 16:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 4:03 Ulrich Drepper
2008-04-24 10:25 ` Alan Cox
2008-04-24 12:34 ` Michael Kerrisk
2008-04-24 14:49 ` Ulrich Drepper
2008-04-24 14:42 ` Alan Cox
2008-04-24 15:19 ` Ulrich Drepper
2008-04-24 15:05 ` Michael Kerrisk
2008-04-24 14:18 ` Ulrich Drepper
2008-04-24 14:24 ` Alan Cox
2008-04-24 15:16 ` Ulrich Drepper
2008-04-24 15:03 ` Alan Cox
2008-04-24 15:44 ` Jakub Jelinek
2008-04-24 15:24 ` Alan Cox
2008-04-24 16:00 ` David Miller
2008-04-24 15:38 ` Alan Cox
2008-04-24 16:09 ` David Miller
2008-04-24 16:45 ` Michael Kerrisk
2008-04-26 22:41 ` dean gaudet
2008-04-24 15:45 ` Ulrich Drepper
2008-04-24 15:27 ` Alan Cox
2008-04-24 16:04 ` Ulrich Drepper
2008-04-24 15:45 ` Alan Cox
2008-04-24 16:06 ` Michael Kerrisk
2008-04-24 16:49 ` Evgeniy Polyakov
2008-04-24 15:29 ` Linus Torvalds
2008-04-24 15:39 ` David Miller
2008-04-24 16:03 ` Michael Kerrisk
2008-04-24 15:42 ` Alan Cox
2008-04-24 16:48 ` Michael Kerrisk [this message]
2008-04-24 17:20 ` H. Peter Anvin
2008-04-24 17:31 ` Ulrich Drepper
2008-04-24 17:34 ` H. Peter Anvin
2008-04-24 16:30 ` Linus Torvalds
2008-04-24 16:52 ` Ulrich Drepper
2008-04-24 12:27 ` Michael Kerrisk
2008-04-24 12:46 ` David Collier-Brown
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=517f3f820804240948u788745f4s7a5dd4e7417ffeaf@mail.gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®