From: dborkman@redhat.com (Daniel Borkmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH arm64-next] net: bpf: arm64: address randomize and write protect JIT code
Date: Fri, 12 Sep 2014 19:39:21 +0200 [thread overview]
Message-ID: <54132FC9.5040201@redhat.com> (raw)
In-Reply-To: <20140912172151.GI5532@arm.com>
On 09/12/2014 07:21 PM, Catalin Marinas wrote:
...
> We don't have a brk instruction for arm32 but we have guaranteed
> undefined space. Have a look at the kgdb support for example (or grep
> for register_undef_hook under arch/arm) to get an idea.
Will do, thanks!
>> Last but not least ;), if I would resend it today, would you queue
>> it for later on, or do you want to handle it differently?
>
> You can send it now, it will be pushed upstream at the right time.
Just did, thanks a lot for your help!
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Borkmann <dborkman@redhat.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <Will.Deacon@arm.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"zlim.lnx@gmail.com" <zlim.lnx@gmail.com>,
"ast@plumgrid.com" <ast@plumgrid.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH arm64-next] net: bpf: arm64: address randomize and write protect JIT code
Date: Fri, 12 Sep 2014 19:39:21 +0200 [thread overview]
Message-ID: <54132FC9.5040201@redhat.com> (raw)
In-Reply-To: <20140912172151.GI5532@arm.com>
On 09/12/2014 07:21 PM, Catalin Marinas wrote:
...
> We don't have a brk instruction for arm32 but we have guaranteed
> undefined space. Have a look at the kgdb support for example (or grep
> for register_undef_hook under arch/arm) to get an idea.
Will do, thanks!
>> Last but not least ;), if I would resend it today, would you queue
>> it for later on, or do you want to handle it differently?
>
> You can send it now, it will be pushed upstream at the right time.
Just did, thanks a lot for your help!
next prev parent reply other threads:[~2014-09-12 17:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 7:11 [PATCH arm64-next] net: bpf: arm64: address randomize and write protect JIT code Daniel Borkmann
2014-09-12 7:11 ` Daniel Borkmann
2014-09-12 16:03 ` Catalin Marinas
2014-09-12 16:03 ` Catalin Marinas
2014-09-12 16:21 ` Daniel Borkmann
2014-09-12 16:21 ` Daniel Borkmann
2014-09-12 16:46 ` Catalin Marinas
2014-09-12 16:46 ` Catalin Marinas
2014-09-12 17:10 ` Will Deacon
2014-09-12 17:10 ` Will Deacon
2014-09-12 17:16 ` Daniel Borkmann
2014-09-12 17:16 ` Daniel Borkmann
2014-09-12 17:21 ` Catalin Marinas
2014-09-12 17:21 ` Catalin Marinas
2014-09-12 17:39 ` Daniel Borkmann [this message]
2014-09-12 17:39 ` Daniel Borkmann
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=54132FC9.5040201@redhat.com \
--to=dborkman@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.