Le 24/07/2020 à 23:23, Richard Henderson a écrit :
> When the chroot does not have /proc mounted, we can read neither
> /proc/sys/vm/mmap_min_addr nor /proc/sys/maps.
>
> The enforcement of mmap_min_addr in the host kernel is done by
> the security module, and so does not apply to processes owned
On 7/27/20 4:19 AM, Laurent Vivier wrote:
> Le 24/07/2020 à 23:23, Richard Henderson a écrit :
>> When the chroot does not have /proc mounted, we can read neither
>> /proc/sys/vm/mmap_min_addr nor /proc/sys/maps.
>>
>> The enforcement of mmap_min_addr in the host kernel is done by
>> the security m
Le 24/07/2020 à 23:23, Richard Henderson a écrit :
> When the chroot does not have /proc mounted, we can read neither
> /proc/sys/vm/mmap_min_addr nor /proc/sys/maps.
>
> The enforcement of mmap_min_addr in the host kernel is done by
> the security module, and so does not apply to processes owned
Hi!
On 7/24/20 11:23 PM, Richard Henderson wrote:
> When the chroot does not have /proc mounted, we can read neither
> /proc/sys/vm/mmap_min_addr nor /proc/sys/maps.
>
> The enforcement of mmap_min_addr in the host kernel is done by
> the security module, and so does not apply to processes owned
When the chroot does not have /proc mounted, we can read neither
/proc/sys/vm/mmap_min_addr nor /proc/sys/maps.
The enforcement of mmap_min_addr in the host kernel is done by
the security module, and so does not apply to processes owned
by root. Which leads pgd_find_hole_fallback to succeed in pr