[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9eb3b5bd-5866-49fb-b4fc-5491cb3d426c@redhat.com>
Date: Thu, 20 Nov 2025 13:33:54 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Tonghao Zhang <tonghao@...aicloud.com>, netdev@...r.kernel.org
Cc: Jay Vosburgh <jv@...sburgh.net>, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Simon Horman <horms@...nel.org>, Jonathan Corbet <corbet@....net>,
Andrew Lunn <andrew+netdev@...n.ch>,
Nikolay Aleksandrov <razor@...ckwall.org>, Hangbin Liu <liuhangbin@...il.com>
Subject: Re: [PATCH net-next v2] net: bonding: use workqueue to make sure peer
notify updated in lacp mode
On 11/18/25 10:03 AM, Tonghao Zhang wrote:
> +static void bond_peer_notify_handler(struct work_struct *work)
> +{
> + struct bonding *bond = container_of(work, struct bonding,
> + peer_notify_work.work);
> +
> + if (!rtnl_trylock())
> + goto rearm;
Why trylock() here? This is process context, you could just call
rtnl_lock();
and no re-schedule.
/P
Powered by blists - more mailing lists