From: Dan Carpenter <dan.carpenter@oracle.com>
To: vladbu@nvidia.com
Cc: linux-rdma@vger.kernel.org
Subject: [bug report] net/mlx5e: Handle FIB events to update tunnel endpoint device
Date: Wed, 10 Feb 2021 14:08:13 +0300 [thread overview]
Message-ID: <YCO+nR+3Zs9jIAfp@mwanda> (raw)
Hello Vlad Buslov,
The patch 8914add2c9e5: "net/mlx5e: Handle FIB events to update
tunnel endpoint device" from Jan 25, 2021, leads to the following
static checker warning:
drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun_encap.c:1639 mlx5e_tc_tun_init()
error: passing non negative 1 to ERR_PTR
drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun_encap.c
1622 struct mlx5e_tc_tun_encap *mlx5e_tc_tun_init(struct mlx5e_priv *priv)
1623 {
1624 struct mlx5e_tc_tun_encap *encap;
1625 int err;
1626
1627 encap = kvzalloc(sizeof(*encap), GFP_KERNEL);
1628 if (!encap)
1629 return ERR_PTR(-ENOMEM);
1630
1631 encap->priv = priv;
1632 encap->fib_nb.notifier_call = mlx5e_tc_tun_fib_event;
1633 spin_lock_init(&encap->route_lock);
1634 hash_init(encap->route_tbl);
1635 err = register_fib_notifier(dev_net(priv->netdev), &encap->fib_nb,
1636 NULL, NULL);
register_fib_notifier() calls fib_net_dump() which eventually calls
fib6_walk_continue() which can return 1 if "walk is incomplete (i.e.
suspended)".
1637 if (err) {
1638 kvfree(encap);
1639 return ERR_PTR(err);
If this returns 1 it will eventually lead to an Oops.
1640 }
1641
1642 return encap;
1643 }
regards,
dan carpenter
next reply other threads:[~2021-02-10 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 11:08 Dan Carpenter [this message]
2021-02-10 11:55 ` [bug report] net/mlx5e: Handle FIB events to update tunnel endpoint device Vlad Buslov
2021-02-10 13:21 ` Ido Schimmel
2021-02-10 13:50 ` Vlad Buslov
2021-02-10 14:01 ` Ido Schimmel
2021-02-10 14:03 ` Dan Carpenter
2021-02-10 14:00 ` Dan Carpenter
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=YCO+nR+3Zs9jIAfp@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-rdma@vger.kernel.org \
--cc=vladbu@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.