Hi.
I'm presently building from source code. It's rather long but it works. I have a custom build, and I'm awaiting for a build with default official config. I don't know yet how to include the patch, but I'm confidend I'll find soon enough.
Hi
Good news. A commit has been submited for solving both kernels 5.10 (22.03 snapshot) and 5.15 (master).
It may be active in the next daily release.
2 Likes
The fix does not correct the builds on 5.4.238 used in the earlier stable release, only the 5.10.x and 5.15.x cuts but leaves the 21.02.6 broken as well as 22.03.4. All stable releases should incorporate the fjx and then be re-issued in these stable branches. The feeling is if the build does not work, then so sad, if the build bricks it, too bad.
2 Likes
I agree that they shouldn't leave the broken releases on the servers, either correct them or remove them.
Personally, I hope for corrected builds, as we are missing the patches for the vulnerabilities exposed in 22.03.4, and a 22.03.5 release might take a while.
1 Like
Agreed.
I'm wondering if I haven't seen such patch amid all that I browsed. I must confess that I focus on 5.10 (current stable) and 5.15 (future).
I can confirm it works for MR8300
with the
Both my EA8300 and MR8300 now boot with OpenWrt 22.03-SNAPSHOT r20127-074db57936 / LuCI openwrt-22.03 branch git-23.093.57104-ce20b4a
THANK YOU!
2 Likes
Good to know the snapshot number that is working!
Awesome, would this mean the next nightly build is safe to install??
Also will there be a fixed version of 22.03.4 soon
Thanks
OpenWrt 22.03-SNAPSHOT r20127-074db57936 / LuCI openwrt-22.03 branch git-23.093.57104-ce20b4a
2 Likes
But these are eko builds, the official openwrt current snapshot works?
1 Like
Not yet, there are from yesterday. I have monitored them all day long.
1 Like
You can compile from that
1 Like
Suggest that you refresh the targets based on UBI fault within the 22.03.4, 21.02.6 trees with builds later than the currently posted r20123 release. Snapshots will automagically see the fix sometime later since the PR had been posted today.
Very good news! I have just compiled a master snapshot for MR8300 and it runs! 
OpenWrt SNAPSHOT r22573-72780e3eac / LuCI Master git-23.104.28202-588c6a1
1 Like
Now if the patch gets applied to all current stable trees for the releases as announced and they are refreshed, the dev team will solve and no longer have to deal with the headache of 'my box just became a brick.' Conducting an inventory now of all potential targets that are impacted by going through the sources for all build devices using the UBI code so that they will be known in advance.
It's unlikely. I have seen last minute issue in previous versions (for example firewall4 last year) and the releases were never "refreshed". A new one is built.
An operational deficiency is diferrent from a severity one problem where the device is rendered inoperable when previously it was not. Solutions are not released to break things, if that is the case then the team is irresponsible in their release manegement strategy.
Still not working with the imagebuilder: it's still stuck to yesterday (r22570). I'll retry tomorrow...