netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Zhengchao Shao <shaozhengchao@huawei.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, andy@greyhouse.net,
	weiyongjun1@huawei.com, yuehaibing@huawei.com
Subject: Re: [PATCH net-next,v4] bonding: return -ENOMEM instead of BUG in alb_upper_dev_walk
Date: Mon, 20 Nov 2023 17:20:01 -0800	[thread overview]
Message-ID: <14621.1700529601@famine> (raw)
In-Reply-To: <20231118081653.1481260-1-shaozhengchao@huawei.com>

Zhengchao Shao <shaozhengchao@huawei.com> wrote:

>If failed to allocate "tags" or could not find the final upper device from
>start_dev's upper list in bond_verify_device_path(), only the loopback
>detection of the current upper device should be affected, and the system is
>no need to be panic.
>So return -ENOMEM in alb_upper_dev_walk to stop walking, print some warn
>information when failed to allocate memory for vlan tags in
>bond_verify_device_path.
>
>I also think that the following function calls
>netdev_walk_all_upper_dev_rcu
>---->>>alb_upper_dev_walk
>---------->>>bond_verify_device_path
>From this way, "end device" can eventually be obtained from "start device"
>in bond_verify_device_path, IS_ERR(tags) could be instead of
>IS_ERR_OR_NULL(tags) in alb_upper_dev_walk.
>
>Signed-off-by: Zhengchao Shao <shaozhengchao@huawei.com>

Acked-by: Jay Vosburgh <jay.vosburgh@canonical.com>

>---
>v4: print information instead of warn
>v3: return -ENOMEM instead of zero to stop walk
>v2: use WARN_ON_ONCE instead of WARN_ON
>---
> drivers/net/bonding/bond_alb.c  | 3 ++-
> drivers/net/bonding/bond_main.c | 5 ++++-
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
>diff --git a/drivers/net/bonding/bond_alb.c b/drivers/net/bonding/bond_alb.c
>index dc2c7b979656..7edf0fd58c34 100644
>--- a/drivers/net/bonding/bond_alb.c
>+++ b/drivers/net/bonding/bond_alb.c
>@@ -985,7 +985,8 @@ static int alb_upper_dev_walk(struct net_device *upper,
> 	if (netif_is_macvlan(upper) && !strict_match) {
> 		tags = bond_verify_device_path(bond->dev, upper, 0);
> 		if (IS_ERR_OR_NULL(tags))
>-			BUG();
>+			return -ENOMEM;
>+
> 		alb_send_lp_vid(slave, upper->dev_addr,
> 				tags[0].vlan_proto, tags[0].vlan_id);
> 		kfree(tags);
>diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
>index 51d47eda1c87..1a40bd08f984 100644
>--- a/drivers/net/bonding/bond_main.c
>+++ b/drivers/net/bonding/bond_main.c
>@@ -2967,8 +2967,11 @@ struct bond_vlan_tag *bond_verify_device_path(struct net_device *start_dev,
> 
> 	if (start_dev == end_dev) {
> 		tags = kcalloc(level + 1, sizeof(*tags), GFP_ATOMIC);
>-		if (!tags)
>+		if (!tags) {
>+			net_err_ratelimited("%s: %s: Failed to allocate tags\n",
>+					    __func__, start_dev->name);
> 			return ERR_PTR(-ENOMEM);
>+		}
> 		tags[level].vlan_proto = BOND_VLAN_PROTO_NONE;
> 		return tags;
> 	}
>-- 
>2.34.1
>
>

  reply	other threads:[~2023-11-21  1:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-18  8:16 [PATCH net-next,v4] bonding: return -ENOMEM instead of BUG in alb_upper_dev_walk Zhengchao Shao
2023-11-21  1:20 ` Jay Vosburgh [this message]
2023-11-21 11:41 ` Paolo Abeni
2023-11-21 12:25   ` shaozhengchao

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=14621.1700529601@famine \
    --to=jay.vosburgh@canonical.com \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shaozhengchao@huawei.com \
    --cc=weiyongjun1@huawei.com \
    --cc=yuehaibing@huawei.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).