From: Mitsuru Chinen <[EMAIL PROTECTED]>
Date: Tue, 9 Oct 2007 16:21:58 +0900
> To judge the timing for DAD, netif_carrier_ok() is used. However,
> there is a possibility that dev->qdisc stays noop_qdisc even if
> netif_carrier_ok() returns true. In that case, DAD NS is not sent out.
> We need to
YOSHIFUJI Hideaki / <[EMAIL PROTECTED]> wrote:
>
> We'd really like to do our best to avoid such random failures
> even if it may/can not be perfect.
OK I see your point of view but there's got to be a better way
than this.
As it is your tests will fail randomly anyway if you do it
Hello.
In article <[EMAIL PROTECTED]> (at Wed, 10 Oct 2007 09:32:35 +0800), Herbert Xu
<[EMAIL PROTECTED]> says:
> Mitsuru Chinen <[EMAIL PROTECTED]> wrote:
> > To judge the timing for DAD, netif_carrier_ok() is used. However,
> > there is a possibility that dev->qdisc stays noop_qdisc even if
>
Mitsuru Chinen <[EMAIL PROTECTED]> wrote:
> To judge the timing for DAD, netif_carrier_ok() is used. However,
> there is a possibility that dev->qdisc stays noop_qdisc even if
> netif_carrier_ok() returns true. In that case, DAD NS is not sent out.
> We need to defer the IPv6 device initialization
To judge the timing for DAD, netif_carrier_ok() is used. However,
there is a possibility that dev->qdisc stays noop_qdisc even if
netif_carrier_ok() returns true. In that case, DAD NS is not sent out.
We need to defer the IPv6 device initialization until a valid qdisc
is specified.
Signed-off-by:
