From: Ruslan Kabatsayev <b7.10110111@gmail.com>
To: Andy Lutomirski <luto@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is it really correct to check for breakpoint in kernel space against ptracer's address space?
Date: Tue, 10 May 2016 14:50:57 +0300 [thread overview]
Message-ID: <CAHEcG96mHpBj4LxTx09DZtrsS5ERrkXeX7_RAUPQ8YsM2JFH-w@mail.gmail.com> (raw)
In-Reply-To: <25b7bea4-e319-99b8-ac4b-019f5b2a1904@kernel.org>
On Tue, May 10, 2016 at 6:33 AM, Andy Lutomirski <luto@kernel.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.
next prev parent reply other threads:[~2016-05-10 11:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 8:43 Is it really correct to check for breakpoint in kernel space against ptracer's address space? Ruslan Kabatsayev
2016-05-10 3:33 ` Andy Lutomirski
2016-05-10 11:50 ` Ruslan Kabatsayev [this message]
2016-05-10 15:23 ` Andy Lutomirski
2016-05-10 15:40 ` Ruslan Kabatsayev
2016-05-10 16:10 ` Andy Lutomirski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHEcG96mHpBj4LxTx09DZtrsS5ERrkXeX7_RAUPQ8YsM2JFH-w@mail.gmail.com \
--to=b7.10110111@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).