Messages in this thread | | | From | Vladimir Oltean <> | Subject | Re: [PATCH AUTOSEL 5.10 22/34] net/sched: taprio: taprio_dump and taprio_change are protected by rtnl_mutex | Date | Tue, 18 Oct 2022 10:03:23 +0000 |
| |
On Tue, Oct 18, 2022 at 12:46:53PM +0300, Vladimir Oltean wrote: > On Tue, Oct 18, 2022 at 11:44:15AM +0200, Pavel Machek wrote: > > Hi! > > > > > From: Vladimir Oltean <vladimir.oltean@nxp.com> > > > > > > [ Upstream commit 18cdd2f0998a4967b1fff4c43ed9aef049e42c39 ] > > > > > > Since the writer-side lock is taken here, we do not need to open an RCU > > > read-side critical section, instead we can use rtnl_dereference() to > > > tell lockdep we are serialized with concurrent writes. > > > > This is cleanup, not a bugfix. We should not have it in 5.10. > > Agreed, looks like I missed this one when replying to Sasha for all the others.
Ah, I do see that I did in fact respond to this already. https://lore.kernel.org/lkml/20221010133337.4q75fsa6m2v5ttk7@skbuf/
Not sure how you put your eyes on this particular patch?
| |