From: Daniel Borkmann
Date: Mon, 8 May 2017 00:04:09 +0200
> The patch fixes two things at once:
>
> 1) It checks the env->allow_ptr_leaks and only prints the map address to
>the log if we have the privileges to do so, otherwise it just dumps 0
>as we would when kptr_restrict is enabled
On Mon, May 08, 2017 at 12:04:09AM +0200, Daniel Borkmann wrote:
> The patch fixes two things at once:
>
> 1) It checks the env->allow_ptr_leaks and only prints the map address to
>the log if we have the privileges to do so, otherwise it just dumps 0
>as we would when kptr_restrict is enab
On 05/08/2017 12:04 AM, Daniel Borkmann wrote:
The patch fixes two things at once:
1) It checks the env->allow_ptr_leaks and only prints the map address to
the log if we have the privileges to do so, otherwise it just dumps 0
as we would when kptr_restrict is enabled on %pK. Given the la
On Mon, May 8, 2017 at 12:51 AM, Daniel Borkmann wrote:
> On 05/08/2017 12:26 AM, Jann Horn wrote:
>>
>> On Mon, May 8, 2017 at 12:04 AM, Daniel Borkmann
>> wrote:
>>>
>>> The patch fixes two things at once:
>>>
>>> 1) It checks the env->allow_ptr_leaks and only prints the map address to
>>>
On 05/08/2017 12:26 AM, Jann Horn wrote:
On Mon, May 8, 2017 at 12:04 AM, Daniel Borkmann wrote:
The patch fixes two things at once:
1) It checks the env->allow_ptr_leaks and only prints the map address to
the log if we have the privileges to do so, otherwise it just dumps 0
as we woul
The patch fixes two things at once:
1) It checks the env->allow_ptr_leaks and only prints the map address to
the log if we have the privileges to do so, otherwise it just dumps 0
as we would when kptr_restrict is enabled on %pK. Given the latter is
off by default and not every distro sets
On Mon, May 8, 2017 at 12:04 AM, Daniel Borkmann wrote:
> The patch fixes two things at once:
>
> 1) It checks the env->allow_ptr_leaks and only prints the map address to
>the log if we have the privileges to do so, otherwise it just dumps 0
>as we would when kptr_restrict is enabled on %p
