From owner-freebsd-current Sat May 16 05:36:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09433 for freebsd-current-outgoing; Sat, 16 May 1998 05:36:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09419; Sat, 16 May 1998 05:36:39 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id UAA02664; Sat, 16 May 1998 20:36:34 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805161236.UAA02664@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG, kkennawa@physics.adelaide.edu.au Subject: Re: libc corruption In-reply-to: Your message of "Sat, 16 May 1998 22:12:55 +1000." <199805161212.WAA18632@godzilla.zeta.org.au> Date: Sat, 16 May 1998 20:36:34 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > >> >To make it a little easier, perhaps have libc's syscall tables explicitly > >> >generated from the kernel sources and committed. That should make it > >> >a no-brainer to keep them in sync and yet will stop accidental leakage > >> >from the kernel into libc. > >> > >> Better yet, generate the tables explicity and don't commit them anywhere. > >> That should make it a no-brainer to keep them in sync and stop accidental > >> blockage of the flow from the kernel into libc :-). > > > >This is the present situation and it's not working very well. > > It isn't the present situation. We commit the tables to src/sys and > use some tables from , some from src/sys/sys, and even some from > src/sys/kern (see src/usr.bin/kdump/kdump.c). We only generate the > tables on the fly for truss (see src/usr.bin/truss/Makefile). I'm talking about libc.. The syscall stub list is generated on the fly and the binary interface is affected. Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message