[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#340953: marked as done (linux-2.6: oops when asking ipv6 route when no public address?)



Your message dated Fri, 3 Aug 2007 17:12:52 +0200
with message-id <20070803151252.GA26596@stro.at>
and subject line linux-2.6: oops when asking ipv6 route when no public address?
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: linux-image-2.6.12-1-amd64-k8
Version: 2.6.12-10

Hi,

I do have the ipv6 module loaded, have a (default) link local
address assigned, but don't have any global ipv6 addresses.
This is basicly just loading the ipv6 module and doing nothing
else.

When I did the following command:
ip route get 2001:14b0:202:1::a7

I got an oops:
Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
<ffffffff881a7d6e>{:ipv6:ipv6_get_saddr+14}
PGD 6472f067 PUD 2e201067 PMD 0
Oops: 0000 [1]
CPU 0
Modules linked in: md5 ipv6 parport_pc parport floppy evdev pcspkr i2c_amd756 hw_random i2c_amd8111 i2c_core amd74xx tpm_nsc tpm_atmel tpm shpchp pci_hotplug ohci_hcd tg3 ext2 rtc psmouse ide_generic ide_disk ide_cd cdrom ide_core ext3 jbd
mbcache sd_mod sata_sil libata scsi_mod raid0 md unix fbcon tileblit font bitblit vesafb cfbcopyarea cfbimgblt cfbfillrect softcursor
Pid: 13701, comm: ip Not tainted 2.6.12-1-amd64-k8
RIP: 0010:[<ffffffff881a7d6e>] <ffffffff881a7d6e>{:ipv6:ipv6_get_saddr+14}
RSP: 0018:ffff81006f839a10  EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff81006f839a48 RCX: 0000000000000000
RDX: ffff81006f839a48 RSI: ffff81006f839ac0 RDI: ffffffff881dae20
RBP: ffff810006514680 R08: 0000000000000000 R09: 0000000000000018
R10: 0000000000000000 R11: ffff81006f839ac0 R12: ffffffff881dae20
R13: ffff8100309d20b8 R14: 0000000000000000 R15: ffff81006f839ac0
FS:  00002aaaaaf15d40(0000) GS:ffffffff8040f940(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 000000004e43b000 CR4: 00000000000006e0
Process ip (pid: 13701, threadinfo ffff81006f838000, task ffff81007e6569e0)
Stack: ffffffff881aa538 ffff810006514680 0000000000000296 0000000000000000
       ffffffff881abc48 0000000000000246 ffff81006f839ad0 ffff81007e6569e0
       0000000300000282 ffff810006514680
Call Trace:<ffffffff881aa538>{:ipv6:rt6_fill_node+712} <ffffffff881abc48>{:ipv6:ip6_route_output+1256}
       <ffffffff881abe01>{:ipv6:inet6_rtm_getroute+353} <ffffffff80269b7f>{rtnetlink_rcv+623}
       <ffffffff8027a6c2>{netlink_data_ready+18} <ffffffff802788ce>{netlink_sendskb+46}
       <ffffffff8027a447>{netlink_sendmsg+759} <ffffffff8025877b>{sock_sendmsg+283}
       <ffffffff80144e00>{autoremove_wake_function+0} <ffffffff80144e00>{autoremove_wake_function+0}
       <ffffffff80157ac8>{buffered_rmqueue+536} <ffffffff80157bcc>{__alloc_pages+188}
       <ffffffff80257d25>{move_addr_to_kernel+37} <ffffffff802593aa>{sys_sendmsg+586}
       <ffffffff8011efd3>{do_page_fault+1171} <ffffffff801651e2>{do_brk+498}
       <ffffffff8010e67a>{system_call+126}

Code: 48 8b 00 48 89 c7 e9 b7 fd ff ff 66 66 66 90 66 66 90 48 81
RIP <ffffffff881a7d6e>{:ipv6:ipv6_get_saddr+14} RSP <ffff81006f839a10>
CR2: 0000000000000000

I assume it's trying to get the source address, and there
isn't any that can reach that host, because I don't have
any global ipv6 address assigned.


Kurt




--- End Message ---
--- Begin Message ---
Package: linux-2.6
Version: 2.6.22-1

 ip route get 2001:14b0:202:1::a7
 unreachable 2001:14b0:202:1::a7 dev lo  table unspec  proto none  src ::1 metric -1  error -101 advmss 1404 hoplimit 255


and no oops, have disabled ipv6 on our 2.6.18 kernels
thus no easy test atm, but i guess this should have been already
fixed earlier.


-- 
maks

--- End Message ---

Reply to: