From: "Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
To: "p.cheynier@criteo.com" <p.cheynier@criteo.com>,
"kuba@kernel.org" <kuba@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Sokolowski, Jan" <jan.sokolowski@intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Loktionov, Aleksandr" <aleksandr.loktionov@intel.com>
Subject: Re: [5.10] i40e/udp_tunnel: RTNL: assertion failed at net/ipv4/udp_tunnel_nic.c
Date: Tue, 2 Feb 2021 16:55:10 +0000 [thread overview]
Message-ID: <cb0550a3b50269b1eee4b93689792dcb0bb66a19.camel@intel.com> (raw)
In-Reply-To: <20210202083035.3d54f97c@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Tue, 2021-02-02 at 08:30 -0800, Jakub Kicinski wrote:
> On Tue, 2 Feb 2021 09:59:56 +0000 Pierre Cheynier wrote:
> > On Sat, 30 Jan 2021 04:27:00 +0100 Jakub Kicinski wrote:
> >
> > > I must have missed that i40e_setup_pf_switch() is called from the
> > > probe
> > > path.
> >
> > Do you want me to apply these patches, rebuild and tell you what's
> > the
> > outcome?
>
> I was hoping someone from Intel would step in and help.
I inquired with the i40e team about these proposed fixes. Adding a
couple of developers directly.
next prev parent reply other threads:[~2021-02-02 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 17:44 [5.10] i40e/udp_tunnel: RTNL: assertion failed at net/ipv4/udp_tunnel_nic.c Pierre Cheynier
2021-01-30 3:27 ` Jakub Kicinski
2021-02-02 9:59 ` Pierre Cheynier
2021-02-02 16:30 ` Jakub Kicinski
2021-02-02 16:55 ` Nguyen, Anthony L [this message]
2021-02-03 14:23 ` [Intel-wired-lan] " Sokolowski, Jan
2021-02-03 15:25 ` Pierre Cheynier
2021-02-03 16:05 ` Pierre Cheynier
2021-02-03 17:08 ` Jakub Kicinski
2021-02-08 9:09 ` Pierre Cheynier
2021-02-10 8:23 ` Sokolowski, Jan
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=cb0550a3b50269b1eee4b93689792dcb0bb66a19.camel@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jan.sokolowski@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=p.cheynier@criteo.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).