[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <29109394-30ee-48be-b2e9-dd26e5aa9e28@phunq.net>
Date: Wed, 27 May 2015 11:09:25 -0700
From: Daniel Phillips <daniel@...nq.net>
To: Pavel Machek <pavel@....cz>
Cc: Rik van Riel <riel@...hat.com>, <linux-kernel@...r.kernel.org>,
<linux-fsdevel@...r.kernel.org>, <tux3@...3.org>,
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
<mgorman@...e.de>, Andrea Arcangeli <aarcange@...hat.com>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [FYI] tux3: Core changes
On Wednesday, May 27, 2015 12:41:37 AM PDT, Pavel Machek wrote:
> On Fri 2015-05-15 02:38:33, Daniel Phillips wrote:
>> On 05/14/2015 08:06 PM, Rik van Riel wrote: ...
>
> Umm. Why do you think it is only issue for executable files?
I meant: files with code in them, that will be executed. Please excuse
me for colliding with the chmod sense. I will say "code files" to avoid
ambiguity.
> I'm free to mmap() any file, and then execute from it.
>
> /lib/ld-linux.so /path/to/binary
>
> is known way to exec programs that do not have x bit set.
So... why would I write to a code file at the same time as stepping
through it with ptrace? Should I expect ptrace to work perfectly if
I do that? What would "work perfectly" mean, if the code is changing
at the same time as being traced?
Regards,
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists