Re: [PATCH v2 3/3] selftests/mm: virtual_address_range: Avoid reading VVAR mappings

2025-01-13 Thread David Hildenbrand
On 13.01.25 10:09, Thomas Weißschuh wrote: On Fri, Jan 10, 2025 at 04:41:03PM +0100, David Hildenbrand wrote: On 10.01.25 14:05, Thomas Weißschuh wrote: The virtual_address_range selftest reads from the start of each mapping listed in /proc/self/maps. However not all mappings are valid to be ar

Re: [PATCH v2 3/3] selftests/mm: virtual_address_range: Avoid reading VVAR mappings

2025-01-13 Thread Thomas Weißschuh
On Fri, Jan 10, 2025 at 04:41:03PM +0100, David Hildenbrand wrote: > On 10.01.25 14:05, Thomas Weißschuh wrote: > > The virtual_address_range selftest reads from the start of each mapping > > listed in /proc/self/maps. > > However not all mappings are valid to be arbitrarily accessed. > > For examp

Re: [PATCH v2 3/3] selftests/mm: virtual_address_range: Avoid reading VVAR mappings

2025-01-10 Thread David Hildenbrand
On 10.01.25 14:05, Thomas Weißschuh wrote: The virtual_address_range selftest reads from the start of each mapping listed in /proc/self/maps. However not all mappings are valid to be arbitrarily accessed. For example the vvar data used for virtual clocks on x86 [vvar_vclock] can only be accessed

[PATCH v2 3/3] selftests/mm: virtual_address_range: Avoid reading VVAR mappings

2025-01-10 Thread Thomas Weißschuh
The virtual_address_range selftest reads from the start of each mapping listed in /proc/self/maps. However not all mappings are valid to be arbitrarily accessed. For example the vvar data used for virtual clocks on x86 [vvar_vclock] can only be accessed if 1) the kernel configuration enables virtua