From: Dave Jones <davej@suse.de>
To: Ben Clifford <benc@hawaga.org.uk>
Cc: linux-kernel@vger.kernel.org, davem@redhat.com, acme@conectiva.com.br
Subject: Re: Linux 2.5.5-dj1 - IPv6 not loading correctly.
Date: Mon, 25 Feb 2002 22:32:03 +0100 [thread overview]
Message-ID: <20020225223203.C27081@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0202241300100.11220-100000@barbarella.hawaga.org.uk> <Pine.LNX.4.33.0202242203080.21716-100000@barbarella.hawaga.org.uk>
In-Reply-To: <Pine.LNX.4.33.0202242203080.21716-100000@barbarella.hawaga.org.uk>; from benc@hawaga.org.uk on Sun, Feb 24, 2002 at 10:16:16PM -0800
On Sun, Feb 24, 2002 at 10:16:16PM -0800, Ben Clifford wrote:
> Looking at the code, the the ICMP6 control socket error is occurring
> because sock_register isn't called for inet6 until after the ICMP6 control
> socket is created (in af_inet6.c).
> However, the ICMP6 control socket create calls sock_create, which requires
> sock_register to have already been called.
This probably happened during acme's recent protocol cleanups,
and is probably a problem in mainline as well as -dj.
> I have made the below change, which moves the protocol family registration
> higher up in the code. It seems to make ipv6 work now.
>
> However, I'm concerned that this gives a small amount of time when the
> family is registered but not fully initialised.
> Is this bad?
I'll let davem/acme comment on the correctness of the fix..
Looks straightforward enough to me, but I'm not as kneedeep in
networking internals as those two 8-)
>
> - --- /mnt/dev/hda11/2.5.5-dj1-snark-not-changed-much/net/ipv6/af_inet6.c Tue Feb 19 18:10:53 2002
> +++ 2.5.5-dj1/net/ipv6/af_inet6.c Sun Feb 24 22:13:38 2002
> @@ -675,6 +675,13 @@
> */
> inet6_register_protosw(&rawv6_protosw);
>
> + /* register the family here so that the init calls below will
> + * work. ?? is this dangerous ??
> + */
> +
> + (void) sock_register(&inet6_family_ops);
> +
> +
> /*
> * ipngwg API draft makes clear that the correct semantics
> * for TCP and UDP is to consider one TCP and UDP instance
> @@ -719,9 +726,6 @@
> udpv6_init();
> tcpv6_init();
>
> - - /* Now the userspace is allowed to create INET6 sockets. */
> - - (void) sock_register(&inet6_family_ops);
> - -
> return 0;
>
> #ifdef CONFIG_PROC_FS
>
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-02-25 21:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 23:37 Linux 2.5.5-dj1 - Bug Reports Benjamin Pharr
2002-02-22 1:21 ` Dave Jones
2002-02-22 1:23 ` Vojtech Pavlik
2002-02-23 21:28 ` Pavel Machek
2002-02-24 21:00 ` Linux 2.5.5-dj1 - problem with /dev/input/mice Ben Clifford
2002-02-24 21:27 ` Vojtech Pavlik
2002-02-24 21:42 ` Ben Clifford
2002-02-24 21:45 ` Vojtech Pavlik
2002-02-28 9:58 ` Pavel Machek
2002-02-22 6:37 ` Linux 2.5.5-dj1 - Bug Reports Nathan Walp
2002-02-28 16:59 ` Nathan Walp
2002-02-28 19:57 ` Benjamin Pharr
2002-02-28 20:47 ` Dave Jones
2002-03-01 18:12 ` Manfred Spraul
2002-02-24 21:02 ` Linux 2.5.5-dj1 - IPv6 not loading correctly Ben Clifford
2002-02-25 6:16 ` Ben Clifford
2002-02-25 21:32 ` Dave Jones [this message]
2002-02-25 22:18 ` David S. Miller
2002-02-27 20:23 ` Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020225223203.C27081@suse.de \
--to=davej@suse.de \
--cc=acme@conectiva.com.br \
--cc=benc@hawaga.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.