* Puneet Kumar Yatnal via Gcc-bugs:
> What is next step here? How do I post this in Bugzilla and get
> support.
This issue has already been fixed with this commit:
commit 80fe172ba9820199c2bbce5d0611ffca27823049
Author: Jonathan Wakely
Date: Tue Nov 9 23:45:36 2021 +
libstdc++: Disab
* Alexander Popov:
> Of course, there is a naive solution for this issue -- just skip stackleak
> instrumentation for acpi_duplicate_processor_id(). But it would be great to
> find
> out the reasons behind this compiler behavior. It might help to create a
> better
> solution.
Please show us the
* Don Viszneki:
> I'm using standard Ubuntu releases of gcc (5.4.0) and gdb (7.11.1) and I
> have a very simple to reproduce issue on x86-64.
>
> I think I've included all the necessary information in this paste:
>
> https://gist.github.com/hdon/3f96a8a6b67e078e0213660ec6245677
This is likely a l
process_block (buffer, len & ~63, ctx);
This should work, but it looks a bit fishy.
--
Florian Weimer / Red Hat Product Security Team
