From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: drepper@redhat.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
akpm@linux-foundation.org, davidel@xmailserver.org,
mtk.manpages@gmail.com, torvalds@linux-foundation.org,
yoshfuji@linux-ipv6.org
Subject: Re: [PATCH 02/18] flag parameters: socket and socketpair
Date: Mon, 05 May 2008 13:24:52 +0900 (JST) [thread overview]
Message-ID: <20080505.132452.98853465.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <200805050342.m453gktl029817@devserv.devel.redhat.com>
In article <200805050342.m453gktl029817@devserv.devel.redhat.com> (at Sun, 4 May 2008 23:42:46 -0400), Ulrich Drepper <drepper@redhat.com> says:
> This patch adds support for flag values which are ORed to the type passwd
> to socket and socketpair. The additional code is minimal. Beside
> decoding the flags with the library function introduced in a prior patch
> all that has to be done is to pass the new value around.
>
> The internal functions sock_alloc_fd and sock_map_fd get a new parameters
> and all callers are changed.
Well, this seems the only patch that overrides basic context of the
arguments. (Or, we have already "flags" argument for other APIs
that do not require new API.)
To me, it seems overriding 2nd argument is a too ad-hoc workaround,
and introducing new syscalls with flags is cleaner, e.g.,
psocket(family, socktype, protocol, flags);
psocketpair(d, type, protocol, int sv[2], flags);
--yoshfuji
next prev parent reply other threads:[~2008-05-05 4:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 3:42 Ulrich Drepper
2008-05-05 4:24 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2008-05-05 5:00 ` Ulrich Drepper
2008-05-05 8:11 ` David Miller
2008-05-06 1:58 ` Andrew Morton
2008-05-06 2:13 ` Davide Libenzi
2008-05-06 2:17 ` Andrew Morton
2008-05-06 2:30 ` Davide Libenzi
2008-05-06 11:43 ` Alan Cox
2008-05-06 2:33 ` Ulrich Drepper
2008-05-06 2:42 ` Andrew Morton
2008-05-06 2:58 ` Ulrich Drepper
2008-05-06 3:05 ` Andrew Morton
2008-05-06 3:10 ` Ulrich Drepper
2008-05-06 3:02 ` 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=20080505.132452.98853465.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--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®