We pondered if this warrants a release notes entry or not, but there is
nothing in the Archive that is affected nor something in the archive
that we'd change to fix it. Hence it feels wrong to do that.
What bug would we refer to? Just the upstream case - but then I'm sure a
jump of kernel versions needs adaptations in hundreds of more places and
we do not mention them either.
This place and bug report here is appropriate - search engines and user
can find it, it summarized the state and it explains why we are not
affected in any direct way. It links to the upstream case in tcmalloc
for reference and that contains how this will evolve.
TBH the fight between kernel and tcmalloc who broke whom or who relied
on behavior not meant to rely on is not our fight. I'm sure they will
find a compromise that works and then release either a tcmalloc change
(and since the tcmalloc in Ubuntu does not have the affected code that
is a no-op) or a kernel change (in which case the kernel will pick it
up). For the potential of the latter I'll add a kernel bug task but mark
it incomplete for now (as there is nothing to act on, but good to have
them aware).
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2146842
Title:
tcmalloc RSEQ ABI violation causes crashes on linux kernel 6.19+
To manage notifications about this bug go to:
https://bugs.launchpad.net/pkg-google-perftools/+bug/2146842/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
