From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261344AbTKGDvz (ORCPT ); Thu, 6 Nov 2003 22:51:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263853AbTKGDvz (ORCPT ); Thu, 6 Nov 2003 22:51:55 -0500 Received: from yue.hongo.wide.ad.jp ([203.178.139.94]:64016 "EHLO yue.hongo.wide.ad.jp") by vger.kernel.org with ESMTP id S261344AbTKGDvx (ORCPT ); Thu, 6 Nov 2003 22:51:53 -0500 Date: Fri, 07 Nov 2003 12:52:02 +0900 (JST) Message-Id: <20031107.125202.755842752.yoshfuji@linux-ipv6.org> To: jeff.zheng@intel.com Cc: linux-kernel@vger.kernel.org Subject: Re: Why size of sockaddr smaller than size of sockaddr_in6? From: YOSHIFUJI Hideaki / =?iso-2022-jp?B?GyRCNUhGIzFRTEAbKEI=?= In-Reply-To: <37FBBA5F3A361C41AB7CE44558C3448E011959C7@pdsmsx403.ccr.corp.intel.com> References: <37FBBA5F3A361C41AB7CE44558C3448E011959C7@pdsmsx403.ccr.corp.intel.com> Organization: USAGI Project X-URL: http://www.yoshifuji.org/%7Ehideaki/ X-Fingerprint: 90 22 65 EB 1E CF 3A D1 0B DF 80 D8 48 07 F8 94 E0 62 0E EA X-PGP-Key-URL: http://www.yoshifuji.org/%7Ehideaki/hideaki@yoshifuji.org.asc X-Face: "5$Al-.M>NJ%a'@hhZdQm:."qn~PA^gq4o*>iCFToq*bAi#4FRtx}enhuQKz7fNqQz\BYU] $~O_5m-9'}MIs`XGwIEscw;e5b>n"B_?j/AkL~i/MEaZBLP X-Mailer: Mew version 2.2 on XEmacs 21.4.6 (Common Lisp) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org In article <37FBBA5F3A361C41AB7CE44558C3448E011959C7@pdsmsx403.ccr.corp.intel.com> (at Fri, 7 Nov 2003 11:00:55 +0800), "Zheng, Jeff" says: > Is sockaddr_storage part of IPv6? I mean, does sockaddr_storage exist in a system that does not have IPv6? In such system if I use sockaddr_in6, the compile will be failed because there is no sockaddr_in6 structure. AFAIK, sockaddr_storage{} was introduced because sockaddr_in6{} is too large for sockaddr{}. However, the use of sockaddr_storage{} is not limited to IPv6. Systems which does not support IPv6 may have sockaddr_storage{}. BTW, there're little chances for users to use sockaddr_in{} or sockaddr_in6{}. Modern and "good" applications never use them. Use getaddrinfo(3) / getnameinfo(3) (which uses addrinfo{} and sockaddr{}). If you need a structure to hold socket address, you may use sockaddr_storage{}; i.e. for getsockname(2) / getpeername(2). If you are UNABLE to avoid touching socket address structure, use it finally; This is very rare. Well, this is kernel developmen list. Please change the list. Thanks. -- Hideaki YOSHIFUJI @ USAGI Project GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA