Bug? Kernel panic if a special IPv6 address is assigned to an interface

[Peter Bieringer <pb@xxxxxxxxxxxx>]

Hi,

Konstantin Agouros <Konstantin.Agouros@xxxxxxxxx> sends me a hint and I
have reproduced this similar.

The szenario is stupid, but can be happen:

An IPv6 ready 2.2.16 kernel boots up without no additional IPv6 configuration

[root@gate internet]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:BF:06:AE:08
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::250:bfff:fe06:ae08/10 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:340638 errors:0 dropped:0 overruns:0 frame:0
          TX packets:494933 errors:0 dropped:0 overruns:0 carrier:0
          collisions:4288 txqueuelen:100
          Interrupt:9 Base address:0xf800


Konstantin has now assigned a second IPv6 address, and because of
mistyping/misthinking he used

ifconfig eth0 add fe90::250:bfff:fe06:ae08/10
                    ^
after a while, kernel crashes

I reproduced this in similar way, I've added an fe90::EUI address and
delete it few seconds after. Starting reboot, kernel crashes after changing
the runlevel to 6.

On another host on the link I've looked for IPv6 multicasts with tcpdump,
they are received in correct manner.

Can anyone also reproduce this? Does the output of kernel panic help?

Any hints?

TIA,
        Peter