[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALkFLLLYZBE=EztO_1Ws=G+URhBVaLfdvm0v2xRK6ZEEcNBsSg@mail.gmail.com>
Date: Sat, 2 Aug 2025 11:45:27 +0530
From: Ujwal Kundur <ujwal.kundur@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: syzbot+8182574047912f805d59@...kaller.appspotmail.com, davem@...emloft.net,
edumazet@...gle.com, horms@...nel.org, kuba@...nel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org, pabeni@...hat.com,
syzkaller-bugs@...glegroups.com, jiri@...nulli.us, andrew+netdev@...n.ch
Subject: Re: [RFC PATCH] net: team: switch to spinlock in team_change_rx_flags
> This is already fixed by:
> bfb4fb77f9a8 ("team: replace team lock with rtnl lock")
Thanks for letting me know. I now understand ASSERT_RTNL() is a viable
alternative.
> I'm guessing, but is this about passing ndo_set_rx_mode from the upper
> device down to the lower devices? Maybe look at how this is
> implemented for other stacked devices. A VLAN interface on a base
> interface for example? A bridge interface on top of an interface.
Oh this is about stacked devices, hence the references to "lower" and
"upper". Thanks, I'll read more about them.
Powered by blists - more mailing lists