Date: Mon, 25 Aug 2003 23:10:42 -0600 From: "Kenneth D. Merry" <ken@kdm.org> To: Jeffrey Hsu <hsu@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/conf options src/sys/i386/conf LINT src/sys/kern uipc_socket.c src/sys/netgraph ng_ksocket.c src/sys/netinet in.h in_proto.c ip_mroute.c ip_mroute.h ip_output.c ip_var.h raw_ip.c src/sys/sys socketvar.h Message-ID: <20030826051042.GA5487@panzer.kdm.org> In-Reply-To: <20030826042313.GA5014@panzer.kdm.org> References: <200308240824.h7O8OdlX016795@repoman.freebsd.org> <20030826042313.GA5014@panzer.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 25, 2003 at 22:23:13 -0600, Kenneth D. Merry wrote: > On Sun, Aug 24, 2003 at 01:24:39 -0700, Jeffrey Hsu wrote: > > hsu 2003/08/24 01:24:39 PDT > > > > FreeBSD src repository > > > > Modified files: (Branch: RELENG_4) > > sys/conf options > > sys/i386/conf LINT > > sys/kern uipc_socket.c > > sys/netgraph ng_ksocket.c > > sys/netinet in.h in_proto.c ip_mroute.c ip_mroute.h > > ip_output.c ip_var.h raw_ip.c > > sys/sys socketvar.h > > Log: > > Merge from -current support for Protocol Independent Multicast. > > > > Submitted by: Pavlin Radoslavov <pavlin@icir.org> > > > > Revision Changes Path > > 1.191.2.58 +1 -0 src/sys/conf/options > > 1.749.2.152 +4 -0 src/sys/i386/conf/LINT > > 1.68.2.23 +1 -4 src/sys/kern/uipc_socket.c > > 1.5.2.14 +1 -0 src/sys/netgraph/ng_ksocket.c > > 1.48.2.10 +16 -0 src/sys/netinet/in.h > > 1.53.2.7 +15 -1 src/sys/netinet/in_proto.c > > 1.56.2.8 +1390 -37 src/sys/netinet/ip_mroute.c > > 1.17.2.3 +144 -15 src/sys/netinet/ip_mroute.h > > 1.99.2.39 +185 -108 src/sys/netinet/ip_output.c > > 1.50.2.13 +2 -0 src/sys/netinet/ip_var.h > > 1.64.2.16 +8 -0 src/sys/netinet/raw_ip.c > > 1.46.2.10 +1 -1 src/sys/sys/socketvar.h > > This seems to cause a panic when a kernel with the above change is booted > with a userland from Saturday. > > stack trace (copied by hand): > > _end() > rtinit() > if_init() > in_control() > ifioctl() > soo_ioctl() > ioctl() > syscall2() > Xint0x80_syscall() Never mind, it looks like I had a local change that was causing the problem. Sorry for the false alarm. Ken -- Kenneth Merry ken@kdm.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030826051042.GA5487>