Le 25/06/2024 à 17:19, Tom Rini a écrit :
On Tue, Jun 25, 2024 at 03:12:38PM +0000, LEROY Christophe wrote:
Hi All,
Le 24/06/2024 à 21:30, Tom Rini a écrit :
Hey all,
Well, once again I need to check my calender reminders since, whoops,
I'm a week late. That said, looking at the list of changes in this
slightly elongated period, I think it's OK. At this point we're a week
out from the release, so it's time for clear and obvious regression
fixes. Ideally ones introduced this release cycle so there's less
chances of unintended side-effects.
In terms of a changelog,
git log --merges v2024.07-rc4..v2024.07-rc5
contains what I've pulled but as always, better PR messages and tags
will provide better results here.
With that, the final release is planned for Monday, July 1st, 2024.
Thanks all!
For your information, I have started testing v2024.07 on my powerpc
boards in operational condition and I have a major problem : U-boot
doesn't get the Linux kernel started before the watchdog fires. I have
to disable watchdog to get it running.
This problem doesn't occur with v2024.04.
I bisected it to commit 340fdf1303dc ("zlib: Port fix for CVE-2016-9841
to U-Boot") and I also confirm that v2024.07-rc5 works well with that
commit reverted on top of it.
Any idea of what is going wrong with that commit ?
Are you able to check the zlib performance before/after that commit?
Indeed there's a huge difference.
Before : 12298074 timebase ticks to decompress kernel
After : 17145906 ticks, that is 40% more time.
But behind that, we also need to understand why the watchdog is not kept
alive during that time.
Christophe
