From: Oleg Nesterov <oleg@tv-sign.ru>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Michael Kerrisk <mtk.manpages@googlemail.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>,
Davide Libenzi <davidel@xmailserver.org>,
Alan Cox <alan@redhat.com>, Jakub Jelinek <jakub@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
netdev <netdev@vger.kernel.org>,
Roland McGrath <roland@redhat.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: sys_paccept: disable paccept() until API design is resolved
Date: Wed, 17 Sep 2008 18:30:42 +0400 [thread overview]
Message-ID: <20080917143042.GA376@tv-sign.ru> (raw)
In-Reply-To: <48D03E85.9030808@redhat.com>
On 09/16, Ulrich Drepper wrote:
>
> Michael Kerrisk wrote:
>
> > * The behavior of paccept() when interrupted by a signal is IMO
> > strange:
>
> You use your own opinion as the deciding factor?
It would be very strange if Michael used the somebody else's opinion ;)
> The behavior differs
> from other uses but is consistent with the accept() behavior.
And Michael asks why this behaviour (and paccept() itself) is useful.
I must admit I don't understand this too.
It is very possible that we both just need the help from expert (you).
(Ulrich, there is no irony, seriously).
Oleg.
prev parent reply other threads:[~2008-09-17 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 12:05 sys_paccept: disable paccept() until API design is resolved Michael Kerrisk
2008-09-16 13:04 ` Oleg Nesterov
2008-09-16 23:17 ` Ulrich Drepper
2008-09-17 0:24 ` Michael Kerrisk
2008-09-17 16:46 ` Evgeniy Polyakov
2008-09-17 1:22 ` Nick Piggin
2008-09-17 6:50 ` Rémi Denis-Courmont
2008-09-17 14:30 ` Oleg Nesterov [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=20080917143042.GA376@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=davem@davemloft.net \
--cc=davidel@xmailserver.org \
--cc=drepper@redhat.com \
--cc=hch@lst.de \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@googlemail.com \
--cc=netdev@vger.kernel.org \
--cc=roland@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).