[squid-dev] v5.4 backports

[Alex Rousskov]

On 1/18/22 5:31 AM, Amos Jeffries wrote:
> The following changes accepted into v6 are also eligible for v5 but have
> issues preventing me scheduling them.
> 
> 
> This has conflicts I need some assistance resolving. So will not being
> doing the backport myself. If you are interested please open a PR
> against v5 branch for the working backport before Feb 1st.
> 
>  * Bug #5090: Must(!request->pinnedConnection()) violation (#930)
>   squid-6-15bde30c33e47a72650ef17766719a5fc7abee4c

The above fix relies on a Bug #5055 fix (i.e. master/v6 commit 2b6b1bc
mentioned below as a special case).


> The following just need bugzilla IDs. If interested in getting a
> backport please open the bug report with useful details (ie document the
> user-visible behaviour) and then ping me.
> 
>  * Properly track (and mark) truncated store entries (#909)
>    squid-6-ba3fe8d9bc8d35c4b04cecf30cfc7288c57e685c

https://bugs.squid-cache.org/show_bug.cgi?id=5187

>  * Fix reconfiguration leaking tls-cert=... memory (#911)
>    squid-6-b05c195415169b684b6037f306feead45ee9de4e

https://bugs.squid-cache.org/show_bug.cgi?id=5188


>  * Preserve configured order of intermediate CA certificate chain (#956)
>    squid-6-166fb918211b76a0e79eb07967f4d092f74ea18d

https://bugs.squid-cache.org/show_bug.cgi?id=5190

Please do not misinterpret the creation of the above bug reports as an
implicit support for the idea of spending time on creating such bug
reports. I think our time is best spent elsewhere.



>  * Bug #5055: FATAL FwdState::noteDestinationsEnd exception: opening (#877)
>   squid-6-2b6b1bcb8650095c99a1916f5964305484af7ef0

Waiting for a base commit SHA from you.


> and; Fix FATAL ServiceRep::putConnection exception: theBusyConns > 0 (#939)
>   squid-6-a8ac892bab446ac11f816edec53306256bad4de7

This fixes a bug in the Bug #5055 fix AFAICT, so waiting on the
master/v6 commit 2b6b1bc backport (i.e. the previous bullet).


HTH,

Alex.