Re: [PATCH] softmmu: Always initialize xlat in address_space_translate_for_iotlb

2022-06-21 Thread Peter Maydell
On Mon, 20 Jun 2022 at 17:54, Richard Henderson wrote: > > On 6/20/22 05:52, Peter Maydell wrote: > > On Wed, 15 Jun 2022 at 17:43, Richard Henderson > > wrote: > >> > >> The bug is an uninitialized memory read, along the translate_fail > >> path, which results in garbage being read from

Re: [PATCH] softmmu: Always initialize xlat in address_space_translate_for_iotlb

2022-06-20 Thread Richard Henderson
On 6/20/22 05:52, Peter Maydell wrote: On Wed, 15 Jun 2022 at 17:43, Richard Henderson wrote: The bug is an uninitialized memory read, along the translate_fail path, which results in garbage being read from iotlb_to_section, which can lead to a crash in io_readx/io_writex. The bug may be

Re: [PATCH] softmmu: Always initialize xlat in address_space_translate_for_iotlb

2022-06-20 Thread Peter Maydell
On Wed, 15 Jun 2022 at 17:43, Richard Henderson wrote: > > The bug is an uninitialized memory read, along the translate_fail > path, which results in garbage being read from iotlb_to_section, > which can lead to a crash in io_readx/io_writex. > > The bug may be fixed by writing any value with

[PATCH] softmmu: Always initialize xlat in address_space_translate_for_iotlb

2022-06-15 Thread Richard Henderson
The bug is an uninitialized memory read, along the translate_fail path, which results in garbage being read from iotlb_to_section, which can lead to a crash in io_readx/io_writex. The bug may be fixed by writing any value with zero in ~TARGET_PAGE_MASK, so that the call to iotlb_to_section using