Date: Mon, 30 Aug 2004 17:29:22 -0700 From: Peter Wemm <peter@wemm.org> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src UPDATING src/sys/sys param.h src/sys/net if.c if.h Message-ID: <200408301729.22348.peter@wemm.org> In-Reply-To: <20040830215323.GB24404@odin.ac.hmc.edu> References: <200408300629.i7U6TQ5C088279@repoman.freebsd.org> <16691.40287.478937.342838@grasshopper.cs.duke.edu> <20040830215323.GB24404@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 30 August 2004 02:53 pm, Brooks Davis wrote: > On Mon, Aug 30, 2004 at 05:34:23PM -0400, Andrew Gallatin wrote: > > Brooks Davis writes: > > > I don't think so. The main offenders will be programs that walk > > > the interface list via libkvm and programs that use struct > > > if_data. ifconfig does neither. If you haven't recompiled a > > > module, a non-working ifconfig might result if by some miracle > > > you didn't get a panic on attach. > > > > ppc does not even build modules, so that's out. An older ifconfig > > pukes, while a new one works, so some sort of kernel/userland ABI > > must have changed in the last week. Has the data exported by > > sysctl changed recently? > > I think I found it, at least partially. The issue is struct > if_msghdr which is used by ifconfig. It contains a struct if_data. > It has grown by a struct timeval. The weird thing is that this > shouldn't be a problem becuase if_msghdr has a length and my addition > was to the end so ifconfig should be able to skip over it, but it > doesn't seem to actually work. It is broken on amd64 too, FWIW. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408301729.22348.peter>