From owner-freebsd-net@FreeBSD.ORG Tue Sep 21 17:31:01 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92AFC16A4CE; Tue, 21 Sep 2004 17:31:01 +0000 (GMT) Received: from cheer.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2000B43D48; Tue, 21 Sep 2004 17:31:01 +0000 (GMT) (envelope-from ume@FreeBSD.org) Received: from lyrics.mahoroba.org (IDENT:fdX/vnGIgJHJh3Z3M4kmt/muiY23zk454XVLJwXlV+Pd5u/xLZbJQ+1mTf3EbfnQ@lyrics.mahoroba.org [IPv6:3ffe:501:185b:8010:280:88ff:fe03:4841]) (user=ume mech=CRAM-MD5 bits=0)i8LHUuIu033522 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Sep 2004 02:30:56 +0900 (JST) (envelope-from ume@FreeBSD.org) Date: Wed, 22 Sep 2004 02:30:54 +0900 Message-ID: From: Hajimu UMEMOTO To: Thomas Quinot In-Reply-To: <20040921123016.GA41677@melusine.cuivre.fr.eu.org> References: <20040921123016.GA41677@melusine.cuivre.fr.eu.org> User-Agent: xcite1.38> Wanderlust/2.11.3 (Wonderwall) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 5.3-BETA5 MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on cheer.mahoroba.org cc: freebsd-net@freebsd.org Subject: Re: freeaddrinfo(NULL) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 17:31:01 -0000 Hi, >>>>> On Tue, 21 Sep 2004 14:30:16 +0200 >>>>> Thomas Quinot said: thomas> Currently a call to freeaddrinfo (NULL) causes a segfault. Is there any thomas> reason why we should not make that a no-op? This would make freeaddrinfo thomas> behave in a manner consistent with free(3), and also with what happens thomas> on Linux. Because, the behavior of freeaddrinfo (NULL) is undefined in RFC 2553 nor RFC 3493. Having such an assumption is a potentially bug and lose portability. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/