Date: Tue, 14 Nov 2000 09:40:02 -0800 (PST) From: Gerhard Sittig <Gerhard.Sittig@gmx.net> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/22723: panic in socket operation inside jails Message-ID: <200011141740.JAA81822@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/22723; it has been noted by GNATS.
From: Gerhard Sittig <Gerhard.Sittig@gmx.net>
To: freebsd-gnats-submit@FreeBSD.org
Cc:
Subject: Re: kern/22723: panic in socket operation inside jails
Date: Tue, 14 Nov 2000 18:22:37 +0100
On Mon, Nov 13, 2000 at 22:59 +0100, EAB Teuling wrote:
>
> I had the same problem with my kernel, but I ran an ktrace over
> inetd when it was starting, and the last operation attempted
> was a socket call to open a IPv6 socket, which is not a
> supported protocol on my box (neither on yours if I see it
> correctly). The EPROTONOSUPPORT seemed like a perfectly good
> reply to me.
Yes, I must have been some kind of misled there. The failing
operation was not meant for the service's job I expected it to do
(the usual IPv4 stuff), but probably was some unconfigured IPv6
thing. And it failed due to the protocol not being found in the
lines above. Looking over the -CURRENT history of uipc_socket.c
I noticed a change back in mid June which exactly addressed this
very issue. Obviously it hasn't made it back into -STABLE. And
I didn't find it before reporting the problem since the
triggering message was hidden in a mailing list article ...
So I went and applied the patch from
cvs diff -r1.73 -r1.74 sys/kern/uipc_socket.c
(which moves the "prp == 0" check upwards right before
dereferencing the pointer) and commented out the
jail.socket_unixiproute_only=0 line in /etc/sysctl.conf and
everything went fine.
> I'm all in favour for moving the prp == 0 check up, because not
> having protocol installed is what seems to cause the panic.
Yes, that's what fixed it. I just was too blind to see (and know
how to interpret) the socreate() parameters. Unless I'm wrong
again and missing something else ....:)
BTW: Alexey Zakirov was pointing out this exact same solution in
private mail. That's why I don't claim to have found this
solution myself. :>
It seems that -CURRENT has had the fix for half a year now and
-STABLE really needs this commit, too.
virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76
Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net
--
If you don't understand or are scared by any of the above
ask your parents or an adult to help you.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011141740.JAA81822>