linux-kernel - Re: Is it really correct to check for breakpoint in kernel space against ptracer's address space?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHEcG96mHpBj4LxTx09DZtrsS5ERrkXeX7_RAUPQ8YsM2JFH-w@mail.gmail.com>
Date:	Tue, 10 May 2016 14:50:57 +0300
From:	Ruslan Kabatsayev <b7.10110111@...il.com>
To:	Andy Lutomirski <luto@...nel.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Is it really correct to check for breakpoint in kernel space
 against ptracer's address space?

On Tue, May 10, 2016 at 6:33 AM, Andy Lutomirski <luto@...nel.org> wrote:
> Is there any reason at all for TASK_SIZE to be different from TASK_SIZE_MAX?

The distinction originally appears to have been introduced by commit 8492980.