Hi Thomas!
On Fri, 2023-02-10 at 16:52 +0100, Thomas Huth wrote:
> On 10/02/2023 16.23, John Paul Adrian Glaubitz wrote:
> > Hi!
> >
> > There is an unaddressed issue in qemu-user [1] which results in getresuid()
> > returning an incorrect UID due to a byte-swapping issue on sparc64.
>
> Oh,
On 10/02/2023 16.23, John Paul Adrian Glaubitz wrote:
Hi!
There is an unaddressed issue in qemu-user [1] which results in getresuid()
returning an incorrect UID due to a byte-swapping issue on sparc64.
Oh, there are still people out there using qemu-user on sparc64 hosts? ...
that reminds me
On 10/2/23 16:23, John Paul Adrian Glaubitz wrote:
Hi!
There is an unaddressed issue in qemu-user [1] which results in getresuid()
returning an incorrect UID due to a byte-swapping issue on sparc64.
This issue is fixed by the patch below which was suggested by Phillippe
Mathieu-Daudé, but the
Hi!
There is an unaddressed issue in qemu-user [1] which results in getresuid()
returning an incorrect UID due to a byte-swapping issue on sparc64.
This issue is fixed by the patch below which was suggested by Phillippe
Mathieu-Daudé, but the corresponding line [2] has not been patched yet.
