Comment 11 for bug 1947099

> I will attempt to upstream this fix to klibc, but I believe the change to Bionic should happen in parallel/independently since the upstream patch will not make its way back to Bionic (which is stuck at 2.0.4, as mentioned above).

Yes that is the plan to SRU the fix on top of what is currently found in Bionic's klibc.
And I'll gladly sponsor your patch in Bionic.

The idea with upstream is to make our contribution available to other who may suffer from the same issue, make sure it won't re-occur in a future release of Ubuntu as we will sync from debian which sync from upstream, ... and also have some kind of upstream adoption/approval/review of your proposal fix.

Let's give a few days after the submission for the upstream to have some time to review your patch. If it takes too long for them to get back to us, I'll sponsor the patch as-is, knowing that it was submitted to upstream with a reasonable amount of time given to them to review.

- Eric