From owner-freebsd-standards@FreeBSD.ORG Thu Jun 2 19:59:11 2005 Return-Path: X-Original-To: standards@freebsd.org Delivered-To: freebsd-standards@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F05516A41C; Thu, 2 Jun 2005 19:59:11 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 062A443D4C; Thu, 2 Jun 2005 19:59:10 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.4/8.13.4/NETPLEX) with ESMTP id j52Jx7kM019809; Thu, 2 Jun 2005 15:59:07 -0400 (EDT) Date: Thu, 2 Jun 2005 15:59:07 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Hajimu UMEMOTO In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: nectar@freebsd.org, standards@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [CFR] correct type of addrinfo.ai_addrlen and netent.n_net X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2005 19:59:11 -0000 On Fri, 3 Jun 2005, Hajimu UMEMOTO wrote: > Hi, > > >>> On Wed, 01 Jun 2005 21:44:03 +0900 > >>> Hajimu UMEMOTO said: > > ume> I've attached the patch to correct 1st argument of getnetbyaddr(3) in > ume> this mail. It is subset of my previous patch. Since it breaks ABI > ume> compatibility of getnetbyaddr(3), I think it is better to correct > ume> n_net member of struct netent, too. Since there is objection, the > ume> patch leaves struct addrinfo as is. So, it doesn't need to bump any > ume> shlib major. Is it okay? > > Ultimately, I wish to correct struct addrinfo, too. Since correcting > getnetbyaddr(3) breaks ABI compatibility after all, it seems storange > to me to leave struct addrinfo alone as is. It is better to take this > occasion to correct struct addrinfo as well. > This breakage is only on 64 bit arch. The influence will grow as 64 > bit arch spreads. So, I believe it should be done as soon as > possible. Just leave it alone for now. When symbol versioning comes, you should be able to remove the padding without bumping library versions and producing imcompatibilities. -- DE