Re: next OpenWrt 22.03 and 21.02 minor release
Mateusz Jończyk wrote on 06.04.23 14:18: W dniu 28.03.2023 o 00:54, hauke at hauke-m.de (Hauke Mehrtens) pisze: Hi, this paper is about CVE-2022-47522 which seems to be fixed in all supported OpenWrt branches by commits that were pushed 7 days ago by Felix Fietkau. E.g. 4ae854d05568bc36a4df2cb6dd8fb023b5ef9944 in branch openwrt-22.03. Unfortunately, that commit at least breaks ath11k on Xiaomi AX3600 - I know this is not a supported device but wonder if there is other regressions? See https://forum.openwrt.org/t/xiaomi-ax3600-ath11k-failed-to-flush-transmit-queue-and-wifi-disruption/156530 this forum post. Hey there, I just want to give an update on this: Not an issue anymore with current master - My guess is that recent ath11k update and firmware bump to 2.9 for IPQ8074 and QCN9074 devices fixed this bug as well - in any case, I noticed my comment is irrelevant to openwrt-22.03 because it does not include ath11k yet anyway. Sorry for the noise, Matthias ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: next OpenWrt 22.03 and 21.02 minor release
Hi all, Last night we tagged two new point releases for the 22 and 21 releases. I’m traveling right now but will try to write the release notes later today. Best, Paul > On 7. Apr 2023, at 18:31, openwrt-de...@matthias-larisch.de wrote: > > >> >> Mateusz Jończyk wrote on 06.04.23 14:18: >>> W dniu 28.03.2023 o 00:54, hauke at hauke-m.de (Hauke Mehrtens) pisze: Hi, >>> I was wondering whether you would like to delay the release until this is >>> fixed >>> in mainline Linux. >> Hi Mateusz, >> this paper is about CVE-2022-47522 which seems to be fixed in all supported >> OpenWrt branches by commits that were pushed 7 days ago by Felix Fietkau. >> E.g. 4ae854d05568bc36a4df2cb6dd8fb023b5ef9944 in branch openwrt-22.03. >> Greetings, >> Andreas > > Hey there, > > Unfortunately, that commit at least breaks ath11k on Xiaomi AX3600 - I know > this is not a supported device but wonder if there is other regressions? See > https://forum.openwrt.org/t/xiaomi-ax3600-ath11k-failed-to-flush-transmit-queue-and-wifi-disruption/156530 > this forum post. > > (ath11k queue flush fails on disconnect thus interrupting the whole wifi for > a few seconds) > > Greetings, > > Matthias > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: next OpenWrt 22.03 and 21.02 minor release
Mateusz Jończyk wrote on 06.04.23 14:18: W dniu 28.03.2023 o 00:54, hauke at hauke-m.de (Hauke Mehrtens) pisze: Hi, I was wondering whether you would like to delay the release until this is fixed in mainline Linux. Hi Mateusz, this paper is about CVE-2022-47522 which seems to be fixed in all supported OpenWrt branches by commits that were pushed 7 days ago by Felix Fietkau. E.g. 4ae854d05568bc36a4df2cb6dd8fb023b5ef9944 in branch openwrt-22.03. Greetings, Andreas Hey there, Unfortunately, that commit at least breaks ath11k on Xiaomi AX3600 - I know this is not a supported device but wonder if there is other regressions? See https://forum.openwrt.org/t/xiaomi-ax3600-ath11k-failed-to-flush-transmit-queue-and-wifi-disruption/156530 this forum post. (ath11k queue flush fails on disconnect thus interrupting the whole wifi for a few seconds) Greetings, Matthias ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: next OpenWrt 22.03 and 21.02 minor release
W dniu 6.04.2023 o 20:57, Andreas Ziegler pisze: > > Mateusz Jończyk wrote on 06.04.23 14:18: >> W dniu 28.03.2023 o 00:54, hauke at hauke-m.de (Hauke Mehrtens) pisze: >>> Hi, >>> >>> I would like to create a new OpenWrt 22.03 and 21.02 minor release in >>> the next week. >>> >>> OpenWrt 21.02.6 would be the final release of the OpenWrt 21.02 series. >> >> Hello, >> >> Last week, a vulnerability in some WiFi stacks has been revealed. It affects >> Linux and >> can in some cases break WPA2 / WPA3 encryption. It has received much media >> attention. >> >> The paper is called >> "Framing Frames: Bypassing Wi-Fi Encryption by Manipulating Transmit Queues" >> and is authored by Domien Schepers, Aanjhan Ranganathan and Mathy Vanhoef. >> >> I was wondering whether you would like to delay the release until this is >> fixed >> in mainline Linux. >> >> The paper is available at: >> https://papers.mathyvanhoef.com/usenix2023-wifi.pdf >> Some more information from the authors: >> https://github.com/domienschepers/wifi-framing >> >> Greetings, >> >> Mateusz > > > Hi Mateusz, > > this paper is about CVE-2022-47522 which seems to be fixed in all supported > OpenWrt branches by commits that were pushed 7 days ago by Felix Fietkau. > E.g. 4ae854d05568bc36a4df2cb6dd8fb023b5ef9944 in branch openwrt-22.03. > > Greetings, > Andreas Great, thank you for the info. Greetings, Mateusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: next OpenWrt 22.03 and 21.02 minor release
Mateusz Jończyk wrote on 06.04.23 14:18: W dniu 28.03.2023 o 00:54, hauke at hauke-m.de (Hauke Mehrtens) pisze: Hi, I would like to create a new OpenWrt 22.03 and 21.02 minor release in the next week. OpenWrt 21.02.6 would be the final release of the OpenWrt 21.02 series. Hello, Last week, a vulnerability in some WiFi stacks has been revealed. It affects Linux and can in some cases break WPA2 / WPA3 encryption. It has received much media attention. The paper is called "Framing Frames: Bypassing Wi-Fi Encryption by Manipulating Transmit Queues" and is authored by Domien Schepers, Aanjhan Ranganathan and Mathy Vanhoef. I was wondering whether you would like to delay the release until this is fixed in mainline Linux. The paper is available at: https://papers.mathyvanhoef.com/usenix2023-wifi.pdf Some more information from the authors: https://github.com/domienschepers/wifi-framing Greetings, Mateusz Hi Mateusz, this paper is about CVE-2022-47522 which seems to be fixed in all supported OpenWrt branches by commits that were pushed 7 days ago by Felix Fietkau. E.g. 4ae854d05568bc36a4df2cb6dd8fb023b5ef9944 in branch openwrt-22.03. Greetings, Andreas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: next OpenWrt 22.03 and 21.02 minor release
W dniu 28.03.2023 o 00:54, hauke at hauke-m.de (Hauke Mehrtens) pisze: > Hi, > > I would like to create a new OpenWrt 22.03 and 21.02 minor release in > the next week. > > OpenWrt 21.02.6 would be the final release of the OpenWrt 21.02 series. Hello, Last week, a vulnerability in some WiFi stacks has been revealed. It affects Linux and can in some cases break WPA2 / WPA3 encryption. It has received much media attention. The paper is called "Framing Frames: Bypassing Wi-Fi Encryption by Manipulating Transmit Queues" and is authored by Domien Schepers, Aanjhan Ranganathan and Mathy Vanhoef. I was wondering whether you would like to delay the release until this is fixed in mainline Linux. The paper is available at: https://papers.mathyvanhoef.com/usenix2023-wifi.pdf Some more information from the authors: https://github.com/domienschepers/wifi-framing Greetings, Mateusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: next OpenWrt 22.03 and 21.02 minor release
On Tue, Mar 28, 2023 at 11:44 AM Paul Spooren wrote: > > > > How should simple github PRs that are intended be applied to both > > /master and /openwrt-22.03 be handled? > > Feel free to open both at the same time to have the CI running, however be > sure to mark the backport as “draft” and once committed to the main branch, > cherry-pick it with -x so we got a commit reference. > > > (Where the long way would be: first open a PR to /master then come > > back and open another PR to cherry-pick back to /openwrt-22.03) > > We had issues with “trivial” locking backports, skipping a day or two of > waiting isn’t worth the risk in my opinion. Thanks, I will do so now. My own recent PR is such an example, it mistakenly includes a kernel patch for Linux 5.15 which doesn't exist on /openwrt-22.03 , which the CI testing would probably catch :) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: next OpenWrt 22.03 and 21.02 minor release
> On 28. Mar 2023, at 09:09, Joseph Mullally wrote: > >> If we should backport more changes please create a pull request on >> github, send a patch with the 22.03 or 21.02 prefix to the mailing list >> or send a mail with a link to the master commit we should backport as an >> answer to this mail and I will have a look at the commit. > > How should simple github PRs that are intended be applied to both > /master and /openwrt-22.03 be handled? Feel free to open both at the same time to have the CI running, however be sure to mark the backport as “draft” and once committed to the main branch, cherry-pick it with -x so we got a commit reference. > > (Where the long way would be: first open a PR to /master then come > back and open another PR to cherry-pick back to /openwrt-22.03) We had issues with “trivial” locking backports, skipping a day or two of waiting isn’t worth the risk in my opinion. Best, Paul ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: next OpenWrt 22.03 and 21.02 minor release
> If we should backport more changes please create a pull request on > github, send a patch with the 22.03 or 21.02 prefix to the mailing list > or send a mail with a link to the master commit we should backport as an > answer to this mail and I will have a look at the commit. How should simple github PRs that are intended be applied to both /master and /openwrt-22.03 be handled? (Where the long way would be: first open a PR to /master then come back and open another PR to cherry-pick back to /openwrt-22.03) Thanks On Mon, Mar 27, 2023 at 11:57 PM Hauke Mehrtens wrote: > > Hi, > > I would like to create a new OpenWrt 22.03 and 21.02 minor release in > the next week. > > OpenWrt 21.02.6 would be the final release of the OpenWrt 21.02 series. > > On github the following pull requests are tagged for the releases: > https://github.com/openwrt/openwrt/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F22.03 > https://github.com/openwrt/openwrt/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F21.02 > > If we should backport more changes please create a pull request on > github, send a patch with the 22.03 or 21.02 prefix to the mailing list > or send a mail with a link to the master commit we should backport as an > answer to this mail and I will have a look at the commit. > > Hauke > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: next OpenWrt 22.03 and 21.02 minor release
Thanks for the info :) On 3/28/23, Hauke Mehrtens wrote: > Hi, > > I would like to create a new OpenWrt 22.03 and 21.02 minor release in > the next week. > > OpenWrt 21.02.6 would be the final release of the OpenWrt 21.02 series. > > On github the following pull requests are tagged for the releases: > https://github.com/openwrt/openwrt/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F22.03 > https://github.com/openwrt/openwrt/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F21.02 > > If we should backport more changes please create a pull request on > github, send a patch with the 22.03 or 21.02 prefix to the mailing list > or send a mail with a link to the master commit we should backport as an > answer to this mail and I will have a look at the commit. > > Hauke > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: next OpenWrt 22.03 and 21.02 minor release
Hi Hauke,
May I have a little offtopic question about backporting?
I opened a pull request ("comgt: support Mikrotik R11e-LTE6 modem", [1])
where I move a file dependency from "comgt-ncm" to "comgt".
Are such a change allowed to be backported?
[1]: https://github.com/openwrt/openwrt/pull/12261
Thanks,
Szabolcs
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
