[SRU][jammy/linux-azure-5.19, kinetic/linux-azure, lunar/linux-azure][PATCH] Revert "UBUNTU: SAUCE: TDX: Work around the segfault issue in glibc 2.35 in Ubuntu 22.04."
Tim Gardner
tim.gardner at canonical.com
Thu Aug 10 12:29:58 UTC 2023
On 8/10/23 1:38 AM, Stefan Bader wrote:
> On 22.03.23 14:09, Tim Gardner wrote:
>> On 3/22/23 2:40 AM, Stefan Bader wrote:
>>> On 21.03.23 16:27, Ioanna Alifieraki wrote:
>>>> BugLink: https://bugs.launchpad.net/bugs/2011421
>>>>
>>>> This reverts commit 5e304319d26d7003e648bd7a68322537dddbdaed.
>>>
>>> The bug report needs an also-affects for linux-azure. Tim, maybe you
>>> could set things up correctly. I guess jammy:linux-azure-5.19 does
>>> not have to be mentioned or done individually. What is unclear to me
>>> is whether this maybe also affects jammy:linux-azure which, though
>>> its not the default, should also be a possible selection.
>>>
>>> -Stefan
>>>
>>
>> I've updated the bug report with kernel tasks.
>>
>> Jammy linux-azure does not require this revert since it has no TDX
>> support.
>>
>> Only Kinetic linux-azure needs the revert. Jammy linux-azure-5.19 will
>> inherit the revert.
>>
>> Lunar linux-azure requires no change since glibc should be fixed in
>> time for release.
>>
>> As mentioned before, I'll delay applying this revert until after glibc
>> has been released to updates. The kernel glibc patch is benign in the
>> face of a fixed glibc, so overlapping the patched kernel with a fixed
>> glibc should be OK.
>
> Hi Tim, somehow this is still sitting around on the mailing list without
> a clear resolution. By now Kinetic and Jammy 5.19 are out of scope but
> Lunar and with it Jammy 6.2 might be relevant. Is something still
> required or did we just forget to close this?
>
>>
This is still pending. It is waiting on a glibc patch that is still
bubbling up through the SRU process. I expect it will be complete by
next SRU cycle. Then I can implement this revert.
rtg
--
-----------
Tim Gardner
Canonical, Inc
More information about the kernel-team
mailing list