From: Ido Schimmel <idosch@idosch.org>
To: Qian Cai <cai@lca.pw>
Cc: Moshe Shemesh <moshe@mellanox.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Jiri Pirko <jiri@mellanox.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Vladyslav Tarasiuk <vladyslavt@mellanox.com>
Subject: Re: [PATCH net-next v3 5/7] devlink: Add devlink health port reporters API
Date: Mon, 13 Jul 2020 17:07:54 +0300 [thread overview]
Message-ID: <20200713140754.GA238765@shredder> (raw)
In-Reply-To: <20200713131824.GA4489@lca.pw>
On Mon, Jul 13, 2020 at 09:18:25AM -0400, Qian Cai wrote:
> On Fri, Jul 10, 2020 at 03:25:11PM +0300, Moshe Shemesh wrote:
> > From: Vladyslav Tarasiuk <vladyslavt@mellanox.com>
> >
> > In order to use new devlink port health reporters infrastructure, add
> > corresponding constructor and destructor functions.
> >
> > Signed-off-by: Vladyslav Tarasiuk <vladyslavt@mellanox.com>
> > Reviewed-by: Moshe Shemesh <moshe@mellanox.com>
> > Reviewed-by: Jiri Pirko <jiri@mellanox.com>
>
> This will trigger an use-after-free below while doing SR-IOV,
Yes. I sent a patch for internal review and I'm waiting for Vladyslav
and Moshe to review it. Will copy you once I post it.
next prev parent reply other threads:[~2020-07-13 14:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 12:25 [PATCH net-next v3 0/7] Add devlink-health support for devlink ports Moshe Shemesh
2020-07-10 12:25 ` [PATCH net-next v3 1/7] devlink: Refactor devlink health reporter constructor Moshe Shemesh
2020-07-10 12:25 ` [PATCH net-next v3 2/7] devlink: Rework devlink health reporter destructor Moshe Shemesh
2020-07-10 12:25 ` [PATCH net-next v3 3/7] devlink: Create generic devlink health reporter search function Moshe Shemesh
2020-07-10 12:25 ` [PATCH net-next v3 4/7] devlink: Implement devlink health reporters on per-port basis Moshe Shemesh
2020-07-10 12:25 ` [PATCH net-next v3 5/7] devlink: Add devlink health port reporters API Moshe Shemesh
2020-07-13 13:18 ` Qian Cai
2020-07-13 14:07 ` Ido Schimmel [this message]
2020-07-10 12:25 ` [PATCH net-next v3 6/7] net/mlx5e: Move devlink port register and unregister calls Moshe Shemesh
2020-07-10 12:25 ` [PATCH net-next v3 7/7] net/mlx5e: Move devlink-health rx and tx reporters to devlink port Moshe Shemesh
2020-07-10 21:11 ` [PATCH net-next v3 0/7] Add devlink-health support for devlink ports Jakub Kicinski
2020-07-10 21:32 ` 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=20200713140754.GA238765@shredder \
--to=idosch@idosch.org \
--cc=cai@lca.pw \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=vladyslavt@mellanox.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).