From owner-freebsd-hackers Wed Aug 4 10:13: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id 7ED8D1522D; Wed, 4 Aug 1999 10:12:59 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id TAA65943; Wed, 4 Aug 1999 19:13:31 +0200 (CEST) To: "Brian F. Feldman" Cc: Mike Smith , Matthew Dillon , Ollivier Robert , hackers@FreeBSD.org Subject: Re: Jail syscalls References: Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 04 Aug 1999 19:13:30 +0200 In-Reply-To: "Brian F. Feldman"'s message of "Wed, 4 Aug 1999 12:59:44 -0400 (EDT)" Message-ID: <5lpv13o4ed.fsf@assaris.sics.se> Lines: 23 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian F. Feldman" writes: > As I read it, sockaddr is a transparent type (overloaded, as it were). > So we would use something like: > struct jail { > ... > struct sockaddr; > char [SOCK_MAXADDRLEN - sizeof(struct sockaddr)]; > char [sizeof(int) - SOCK_MAXADDRLEN % sizeof(int)];/* padding */ > ... > } Yes, that would work, as would: union { struct sockaddr sa; struct sockaddr_storage ss; } u; I was just trying to say that not all socket addresses fit into a `struct sockaddr' but they should fit into a `struct sockaddr_storage'. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message