From: "David S. Miller" <davem@redhat.com>
To: balbir_soni@hotmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] Suspected bug in getpeername and getsockname
Date: Thu, 17 Jan 2002 13:11:01 -0800 (PST) [thread overview]
Message-ID: <20020117.131101.118630373.davem@redhat.com> (raw)
In-Reply-To: <F96rPJjUsZ6G7KCk5sm0001ad67@hotmail.com>
In-Reply-To: <F96rPJjUsZ6G7KCk5sm0001ad67@hotmail.com>
From: "Balbir Singh" <balbir_soni@hotmail.com>
Date: Thu, 17 Jan 2002 08:27:17 -0800
What I was trying to state is that the protocol specific
code does not get to see the length passed from the user.
The protocol specific code would like to look at what
the user passed.
If move_addr_to_user() takes care of all of the issues, there is no
reason for the protocol specific code to know anything about the
user's len at all.
You have to show me a purpose for it to get passed down. What would
it get used for? All the protocol specific could should (and does)
do is provide the data back to the top level routine and
move_addr_to_user() takes care of the remaining details.
next prev parent reply other threads:[~2002-01-17 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 16:27 [BUG] Suspected bug in getpeername and getsockname Balbir Singh
2002-01-17 20:24 ` kuznet
2002-01-17 21:11 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-18 0:05 Balbir Singh
2002-01-17 23:35 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-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=20020117.131101.118630373.davem@redhat.com \
--to=davem@redhat.com \
--cc=balbir_soni@hotmail.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.