On Mon, Dec 05, 2022 at 11:52:35AM +0100, Johannes Berg wrote:
On Thu, 2022-09-08 at 13:42 +0200, Greg Kroah-Hartman wrote:On Wed, Sep 07, 2022 at 11:29:42AM +0200, Johannes Berg wrote: > On Tue, 2022-09-06 at 16:45 -0400, Sasha Levin wrote: > > On Tue, Sep 06, 2022 at 09:41:54PM +0200, Johannes Berg wrote: > > > On Sat, 2022-08-13 at 16:44 -0400, Sasha Levin wrote: > > > > This is a note to let you know that I've just added the patch titled > > > > > > > > wifi: cfg80211: do some rework towards MLO link APIs > > > > > > > > > > So this happened while I was on vacation, and I didn't really pay > > > attention to stable messages in that period, byt somebody just pointed > > > it out to me ... > > > > > > I don't think it really _hurts_ anything, but why? This is - fairly > > > obviously - a big feature patch on the way to MLO/WiFi7, there's no way > > > any stable kernel will ever really support that? > > > > > > Hmm. It's done of course, and I'm not sure I see a lot of value in going > > > and reverting it either, but it doesn't have a Cc stable, no Fixes tag, > > > nothing there that indicates it fixes anything? Did I do something > > > wrong? > > > > Great question. It was a dependency for backporting: > > Interesting. Yeah I guess I can see that. > > > 36fe8e4e5cb0 ("wifi: mac80211: always free sta in __sta_info_alloc in case of error") > > 55f0a4894484 ("wifi: mac80211: potential NULL dereference in ieee80211_tx_control_port()") > > But then why were those backported? AFAICT, both have fixes tags > pointing to post 6.0-rc1. Yeah, that doesn't seem right. Sasha, can you revert this?That never happened, did it?
No, sorry, I've missed this mail.
There's a regression report on 5.19 related to this backporting: https://bugzilla.kernel.org/show_bug.cgi?id=216711 I'm checking to see if it happens _only_ in 5.19 but I think it does because otherwise we'd probably have seen more activity on that bug, or more bugs about it? So not sure, but maybe there's a chance this regression only happened in 5.19.
I'd note that 5.19 has been EOL for a few months now, users should have moved to 6.0 by now. -- Thanks, Sasha
