From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Ahern <dsahern@gmail.com>, David Ahern <dsahern@kernel.org>,
davem@davemloft.net, jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, rajendra.dendukuri@broadcom.com
Subject: Re: [PATCH net v2] ipv6: Handle race in addrconf_dad_work
Date: Wed, 2 Oct 2019 15:36:47 -0700 [thread overview]
Message-ID: <7bd928cb-1abf-bbae-e1db-505788254e5b@gmail.com> (raw)
In-Reply-To: <45e62fee-1580-4c5d-7cac-5f0db935fa9e@gmail.com>
On 10/2/19 3:33 PM, David Ahern wrote:
> On 10/2/19 4:21 PM, Eric Dumazet wrote:
>> o syzbot this time, but complete lack of connectivity on some of my test hosts.
>>
>> Incoming IPv6 packets go to ip6_forward() (!!!) and are dropped there.
>
> what does 'ip -6 addr sh' show when it is in this state? Any idea of the
> order of events?
This might be related to a use of a bonding device, with a mlx4 slave.
"ip -6 addr sh" shows the same output before/after the patch.
lpaa23:~# ip -6 addr sh dev eth0
2: eth0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 5102 state UP
inet6 2607:f8b0:8099:e17::/128 scope global nodad
valid_lft forever preferred_lft forever
inet6 fe80::21a:11ff:fec3:d7f/64 scope link
valid_lft forever preferred_lft forever
>
> I flipped to IF_READY based on addrconf_ifdown and idev checks seeming
> more appropriate.
>
next prev parent reply other threads:[~2019-10-02 22:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 3:28 [PATCH net v2] ipv6: Handle race in addrconf_dad_work David Ahern
2019-10-01 18:18 ` Eric Dumazet
2019-10-02 21:08 ` Eric Dumazet
2019-10-02 21:23 ` Eric Dumazet
2019-10-02 22:13 ` David Ahern
2019-10-02 22:21 ` Eric Dumazet
2019-10-02 22:33 ` David Ahern
2019-10-02 22:36 ` Eric Dumazet [this message]
2019-10-02 23:11 ` Eric Dumazet
2019-10-02 23:37 ` David Ahern
2019-10-03 0:10 ` David Ahern
2019-10-03 0:36 ` Eric Dumazet
2019-10-03 2:42 ` David Ahern
2019-10-03 15:50 ` David Ahern
2019-10-03 16:32 ` Eric Dumazet
2019-10-03 17:19 ` Eric Dumazet
2019-10-03 19:29 ` David Ahern
2019-10-02 1:45 ` David Miller
2019-10-06 11:46 ` [ipv6] 58a3c210a3: ltp.ping601.fail kernel test robot
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=7bd928cb-1abf-bbae-e1db-505788254e5b@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=rajendra.dendukuri@broadcom.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).