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: Wed, 16 Jan 2002 16:54:48 -0800 (PST) [thread overview]
Message-ID: <20020116.165448.26534238.davem@redhat.com> (raw)
In-Reply-To: <F232Ej1I7QY9zK4unnr000139b2@hotmail.com>
In-Reply-To: <F232Ej1I7QY9zK4unnr000139b2@hotmail.com>
You totally missed what move_addr_to_user() does, which is in fact
truncate the copied len to what the user supplied. Also, the comments
in move_addr_to_user even quote the bits of 1003.1g you a referring
to.
In short, the bug you suggest is not there.
next prev parent reply other threads:[~2002-01-17 0:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 0:51 [BUG] Suspected bug in getpeername and getsockname Balbir Singh
2002-01-17 0:54 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-17 16:27 Balbir Singh
2002-01-17 20:24 ` kuznet
2002-01-17 21:11 ` David S. Miller
2002-01-17 22:11 Balbir Singh
2002-01-17 22:30 ` David S. Miller
2002-01-17 23:20 Balbir Singh
2002-01-17 23:26 ` David S. Miller
2002-01-17 23:35 Balbir Singh
2002-01-17 23:38 ` David S. Miller
2002-01-18 0:05 Balbir Singh
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=20020116.165448.26534238.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox