All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
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 15:35:59 -0800	[thread overview]
Message-ID: <F79oay0q0NTY9agv3Su00012f71@hotmail.com> (raw)


>From: "David S. Miller" <davem@redhat.com>
>
>    Even if we do not pass the value passed by the user
>    to the protocol specific code, I would like to cleanup
>    the code in socket.c to check for invalid values
>    upfront and save time and space in all the calls.
>
>Optimizing error cases never bears any fruit.

In this case, I certainly think it does. Could u give a
case as to why doing this would be harmful? I think the
only issue can be maintainability and doing the change
cleanly. But I think u are a good maintainer and will
accept the changes only if they are properly fixed.
Right :-)

Balbir

_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx


             reply	other threads:[~2002-01-17 23:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 23:35 Balbir Singh [this message]
2002-01-17 23:38 ` [BUG] Suspected bug in getpeername and getsockname David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2002-01-18  0:05 Balbir Singh
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=F79oay0q0NTY9agv3Su00012f71@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.