RFC on Jammy SRU with OpenSSL 3.0 backports for performance

Adrien Nader adrien at notk.org
Tue Aug 29 20:37:37 UTC 2023


On Mon, Aug 28, 2023, Adrien Nader wrote:
> 1- SRU with select patches
> There have been a number of issues reported with upstream patches but
> they had low impact and/or had easy workarounds. Since there are now
> other incentives to do an SRU, I plan to include everything in it.
> I think all patches are in Lunar or even previous releases.
> I don't have a list for performance patches however, except for a couple
> ones. I don't plan to list them by myself; instead I welcome inputs on
> that. Benchmarking is simply too much work, especially considering the
> kind of performance regressions from 1.1 to 3.0 that I've seen talked
> about on the openssl bug tracker. That would probably be a year-long
> full-time job.
> I would like to start preparing this SRU soon and I hope to have it
> ready in October (that's my first SRU this large but I think/hope that's
> realistic). Since it would be the first one, I plan to stick to changes
> that don't require backporting work. For subsequent SRUs we could
> include more patches as Simon said (i.e.  patches from master provided
> they go into non-LTS releases first during their development cycle).

My list of patches so far for the SRU can be seen at this address:


It's likely that the list will be frozen before the end of next weeek.

There's only one thing I'd like to also SRU and which is about removing
dead code that also unecessarily sources debconf in the postinst and
which tends to trigger the infamous bug with thousands of duplicates on
launchpad. Unfortunately I'm not sure I can do that without delaying
this SRU and I might have to leave it for a subsequent one.


More information about the Ubuntu-release mailing list