All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Zhengchao Shao <shaozhengchao@huawei.com>,
	netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, j.vosburgh@gmail.com,
	andy@greyhouse.net, weiyongjun1@huawei.com,
	yuehaibing@huawei.com
Subject: Re: [PATCH net-next,v3] bonding: use WARN_ON instead of BUG in alb_upper_dev_walk
Date: Wed, 15 Nov 2023 17:49:55 +0000	[thread overview]
Message-ID: <20231115174955.GV74656@kernel.org> (raw)
In-Reply-To: <ZVTUL4QByIyGyfDP@nanopsycho>

On Wed, Nov 15, 2023 at 03:22:39PM +0100, Jiri Pirko wrote:
> Wed, Nov 15, 2023 at 12:55:37PM CET, 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.
> >
> >Signed-off-by: Zhengchao Shao <shaozhengchao@huawei.com>
> >---
> >v3: return -ENOMEM instead of zero to stop walk
> >v2: use WARN_ON_ONCE instead of WARN_ON
> 
> Yet the WARN_ON is back :O

Hi Jiri,

I think the suggestion was to either:

1. WARN_ON_ONCE(); return 0;      <= this was v2
2. WARN_ON(); return -ESOMETHING; <= this is v3
(But not, WARN_ON(); return 0;    <= this was v1)

And after v2 it was determined that the approach taken here in v3 is
preferred.

So I think this patch is consistent with the feedback given by Jay
in his reviews so far.

> 
> 
> >---
> > drivers/net/bonding/bond_alb.c | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> >diff --git a/drivers/net/bonding/bond_alb.c b/drivers/net/bonding/bond_alb.c
> >index dc2c7b979656..21f1cb8e453b 100644
> >--- a/drivers/net/bonding/bond_alb.c
> >+++ b/drivers/net/bonding/bond_alb.c
> >@@ -984,8 +984,10 @@ 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();
> >+		if (IS_ERR_OR_NULL(tags)) {
> >+			WARN_ON(1);
> >+			return -ENOMEM;
> >+		}
> > 		alb_send_lp_vid(slave, upper->dev_addr,
> > 				tags[0].vlan_proto, tags[0].vlan_id);
> > 		kfree(tags);
> >-- 
> >2.34.1
> >
> >
> 

  reply	other threads:[~2023-11-15 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15 11:55 [PATCH net-next,v3] bonding: use WARN_ON instead of BUG in alb_upper_dev_walk Zhengchao Shao
2023-11-15 14:22 ` Jiri Pirko
2023-11-15 17:49   ` Simon Horman [this message]
2023-11-15 20:34     ` Jay Vosburgh
2023-11-16 13:58       ` 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=20231115174955.GV74656@kernel.org \
    --to=horms@kernel.org \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=j.vosburgh@gmail.com \
    --cc=jiri@resnulli.us \
    --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 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.