From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Ahern <dsahern@gmail.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
David Miller <davem@davemloft.net>,
alexei.starovoitov@gmail.com
Cc: dsahern@kernel.org, netdev@vger.kernel.org, idosch@mellanox.com,
saeedm@mellanox.com, kafai@fb.com, weiwan@google.com
Subject: Re: [PATCH net-next 0/7] net: add struct nexthop to fib{6}_info
Date: Fri, 31 May 2019 19:34:31 -0700 [thread overview]
Message-ID: <b044ed92-28b3-4743-db87-db84f0c8606b@gmail.com> (raw)
In-Reply-To: <9f57c949-66b6-20d9-2cab-960074616e71@gmail.com>
On 5/31/19 7:29 PM, David Ahern wrote:
> On 5/31/19 7:04 PM, Eric Dumazet wrote:
>>
>> I have a bunch (about 15 ) of syzbot reports, probably caused to your latest patch series.
>>
>> Do we want to stabilize first, or do you expect this new patch series to fix
>> these issues ?
>>
>
> Please forward. I will take a look.
>
I will release one of them, I suspect they are duplicates.
This is why I was looking at rt6_get_pcpu_route()
I thought we were lacking a READ_ONCE() but this does not seem needed.
https://patchwork.ozlabs.org/patch/1108632/
next prev parent reply other threads:[~2019-06-01 2:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 3:07 [PATCH net-next 0/7] net: add struct nexthop to fib{6}_info David Ahern
2019-05-30 3:07 ` [PATCH net-next 1/7] ipv4: Use accessors for fib_info nexthop data David Ahern
2019-05-30 3:07 ` [PATCH net-next 2/7] ipv4: Prepare for fib6_nh from a nexthop object David Ahern
2019-05-30 3:07 ` [PATCH net-next 3/7] ipv4: Plumb support for nexthop object in a fib_info David Ahern
2019-05-30 3:07 ` [PATCH net-next 4/7] ipv6: Plumb support for nexthop object in a fib6_info David Ahern
2019-05-30 3:07 ` [PATCH net-next 5/7] mlxsw: Fail attempts to use routes with nexthop objects David Ahern
2019-05-30 8:10 ` Ido Schimmel
2019-05-30 3:07 ` [PATCH net-next 6/7] mlx5: " David Ahern
2019-05-30 3:08 ` [PATCH net-next 7/7] rocker: " David Ahern
2019-05-30 15:06 ` [PATCH net-next 0/7] net: add struct nexthop to fib{6}_info Alexei Starovoitov
2019-05-30 15:15 ` David Ahern
2019-05-30 15:18 ` Alexei Starovoitov
2019-05-30 18:01 ` David Miller
2019-05-30 18:27 ` Alexei Starovoitov
2019-05-30 18:52 ` David Ahern
2019-05-30 18:57 ` David Miller
2019-05-30 18:58 ` David Ahern
2019-05-30 20:01 ` Alexei Starovoitov
2019-05-31 21:29 ` David Miller
2019-05-31 21:38 ` David Ahern
2019-06-01 1:04 ` Eric Dumazet
2019-06-01 2:29 ` David Ahern
2019-06-01 2:34 ` Eric Dumazet [this message]
2019-06-01 2:38 ` Eric Dumazet
2019-06-01 2:51 ` Alexei Starovoitov
2019-06-01 2:59 ` David Ahern
2019-06-01 3:10 ` Alexei Starovoitov
2019-06-03 16:50 ` Willem de Bruijn
2019-05-30 18:56 ` David Miller
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=b044ed92-28b3-4743-db87-db84f0c8606b@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--cc=idosch@mellanox.com \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=weiwan@google.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).