Re: [PATCH net] bnxt_en: bring back rtnl_lock() in bnxt_fw_reset_task()

[Stanislav Fomichev <stfomichev@gmail.com>]

On 05/12, Jakub Kicinski wrote:
> On Mon, 12 May 2025 16:43:12 -0700 Stanislav Fomichev wrote:
> > On 05/12, Michael Chan wrote:
> > > On Mon, May 12, 2025 at 7:20 AM Stanislav Fomichev <stfomichev@gmail.com> wrote:  
> > > > Will the following work instead? netdev_ops_assert_locked should take
> > > > care of asserting either ops lock or rtnl lock depending on the device
> > > > properties.  
> > > 
> > > It works for netif_set_real_num_tx_queues() but I also need to replace
> > > the ASSERT_RTNL() with netdev_ops_assert_locked(dev) in
> > > __udp_tunnel_nic_reset_ntf().  
> > 
> > Sounds good!
> 
> Mm... To me it sounds concerning. UDP tunnel port tracking doesn't have
> any locks, it depends on RTNL. Are y'all sure we can just drop the
> ASSERT_RTNL() and nothing will blow up? Or did I misunderstand?
> 
> I'd go with Michael's patch for net and revisit in net-next if you're
> filling bold.

Good point. But in this case, we need to cover more? bnxt_open from
bnxt_resume and the callers of bnxt_reset?