I tried my old standby of putting a few printk's to help debug.
I put them in ndisc_output() and ndisc_build_ll_hdr() and they get
printed out ok except when the crash occurs. I get
absolutely nothing. So I do not know where or what are some of
the values ndisc_output() or ndisc_build_ll_addr() are using.
Nothing gets written to my log file when I do the ping6.
I too had been thinking similar to Miyazawa-san...
On Thu, 21 Aug 2003 18:46:40 -0700
"David S. Miller" <davem@xxxxxxxxxx> wrote:
> On Thu, 21 Aug 2003 20:49:47 -0500
> latten@xxxxxxxxxxxxxx wrote:
> > EIP is at ndisc_build_ll_hdr+0x17/0x1e0
> So what exactly is NULL in ndisc_build_ll_hdr(), is
> it 'dev'? That'd be really weird...
I had same crach.
I guess it is due to xfrm cache. My impression about the problem is likes this.
When we configure IPsec and src and dst of neighbour discoery match the
occasionally, The kernel creates and caches the stackable dst like this because
ndisc_send_* want to use it
Then it receives icmpv6 echo request. It replys by using
the cached stackable dst like above. The kernel however must use another
stackable dst like
It is the issue. The kernel can not tell first stackable dst from second
because it can not know the last output function.
I believe we need to change the kernel to use ip6_output ( or another common
to send neighbour discovery packet instead of ndisc_output essentially.
But it may make the kernel be unstable. I think there is not so much request to
with neighbour discovery.
I think it is better to remove xfrm_lookup from ndisc_send_* functions at the