From: "Balbir Singh" <balbir_soni@hotmail.com>
To: davem@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] Suspected bug in getpeername and getsockname
Date: Thu, 17 Jan 2002 16:05:17 -0800 [thread overview]
Message-ID: <F131HApBClrdudfwG9t000112bd@hotmail.com> (raw)
>Can the user eat up more than a scheduling quantum because of the
>work done by ->getname()? I certainly don't think you can prove
>this.
>
That depends on what ->getname() does. Anyway
in my opinion any code which does all the processing
and then catches any error is BROKEN.
>It certainly isn't work the long discussion we're having about it,
>that is for sure.
>
I agree! no point
>You want this to make your broken getname() protocol semantics work
>and I'd like you to address that instead. I get the feeling that
>you've designed this weird behavior and that it is not specified in
>any standard anyways that your protocol must behave in this way. I
>suggest you change it to work without the user length being
>available.
>
There is no other choice but to live with it.
Regards,
Balbir
_________________________________________________________________
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
next reply other threads:[~2002-01-18 0:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-18 0:05 Balbir Singh [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-17 23:35 [BUG] Suspected bug in getpeername and getsockname Balbir Singh
2002-01-17 23:38 ` David S. Miller
2002-01-17 23:20 Balbir Singh
2002-01-17 23:26 ` David S. Miller
2002-01-17 22:11 Balbir Singh
2002-01-17 22:30 ` David S. Miller
2002-01-17 16:27 Balbir Singh
2002-01-17 20:24 ` kuznet
2002-01-17 21:11 ` David S. Miller
2002-01-16 0:51 Balbir Singh
2002-01-17 0:54 ` David S. Miller
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=F131HApBClrdudfwG9t000112bd@hotmail.com \
--to=balbir_soni@hotmail.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.