[kernel-hardening] Re: [RFC PATCH 2/8] thread_info: allow custom in-task thread_info

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Mark Rutland <mark.rutland@arm.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: james.morse@arm.com, AKASHI Takahiro <takahiro.akashi@linaro.org>,
	Kees Cook <keescook@chromium.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	lorenzo.pieralisi@arm.com,
	"kernel-hardening@lists.openwall.com"
	<kernel-hardening@lists.openwall.com>,
	suzuki.poulose@arm.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Will Deacon <will.deacon@arm.com>
Subject: [kernel-hardening] Re: [RFC PATCH 2/8] thread_info: allow custom in-task thread_info
Date: Fri, 23 Sep 2016 18:31:44 +0100	[thread overview]
Message-ID: <20160923173143.GA29830@leverpostej> (raw)
In-Reply-To: <CALCETrV6G2DU1d7qr=ADas7nk5a77=J6X7ezKxw2_kzdmJGDXg@mail.gmail.com>

On Thu, Sep 22, 2016 at 03:23:59PM -0700, Andy Lutomirski wrote:
> On Sep 21, 2016 12:28 AM, "Mark Rutland" <mark.rutland@arm.com> wrote:

> > Given all that, can we make the generic thread_info::flags an unsigned
> > long, matching what the thread flag helpers implicitly assume?
> 
> Yes.  Want to send the patch or should I?

I've sent a patch out to LKML [1], though if that doesn't look right I'm
more than happy for you to send a correct one. ;)

Thanks,
Mark.

[1] http://lkml.kernel.org/r/1474651447-30447-1-git-send-email-mark.rutland@arm.com

WARNING: multiple messages have this Message-ID (diff)

From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/8] thread_info: allow custom in-task thread_info
Date: Fri, 23 Sep 2016 18:31:44 +0100	[thread overview]
Message-ID: <20160923173143.GA29830@leverpostej> (raw)
In-Reply-To: <CALCETrV6G2DU1d7qr=ADas7nk5a77=J6X7ezKxw2_kzdmJGDXg@mail.gmail.com>

On Thu, Sep 22, 2016 at 03:23:59PM -0700, Andy Lutomirski wrote:
> On Sep 21, 2016 12:28 AM, "Mark Rutland" <mark.rutland@arm.com> wrote:

> > Given all that, can we make the generic thread_info::flags an unsigned
> > long, matching what the thread flag helpers implicitly assume?
> 
> Yes.  Want to send the patch or should I?

I've sent a patch out to LKML [1], though if that doesn't look right I'm
more than happy for you to send a correct one. ;)

Thanks,
Mark.

[1] http://lkml.kernel.org/r/1474651447-30447-1-git-send-email-mark.rutland at arm.com

WARNING: multiple messages have this Message-ID (diff)

From: Mark Rutland <mark.rutland@arm.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: james.morse@arm.com, AKASHI Takahiro <takahiro.akashi@linaro.org>,
	Kees Cook <keescook@chromium.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	lorenzo.pieralisi@arm.com,
	"kernel-hardening@lists.openwall.com" 
	<kernel-hardening@lists.openwall.com>,
	suzuki.poulose@arm.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Will Deacon <will.deacon@arm.com>
Subject: Re: [RFC PATCH 2/8] thread_info: allow custom in-task thread_info
Date: Fri, 23 Sep 2016 18:31:44 +0100	[thread overview]
Message-ID: <20160923173143.GA29830@leverpostej> (raw)
In-Reply-To: <CALCETrV6G2DU1d7qr=ADas7nk5a77=J6X7ezKxw2_kzdmJGDXg@mail.gmail.com>

On Thu, Sep 22, 2016 at 03:23:59PM -0700, Andy Lutomirski wrote:
> On Sep 21, 2016 12:28 AM, "Mark Rutland" <mark.rutland@arm.com> wrote:

> > Given all that, can we make the generic thread_info::flags an unsigned
> > long, matching what the thread flag helpers implicitly assume?
> 
> Yes.  Want to send the patch or should I?

I've sent a patch out to LKML [1], though if that doesn't look right I'm
more than happy for you to send a correct one. ;)

Thanks,
Mark.

[1] http://lkml.kernel.org/r/1474651447-30447-1-git-send-email-mark.rutland@arm.com

next prev parent reply	other threads:[~2016-09-23 17:31 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 13:49 [kernel-hardening] [RFC PATCH 0/8] arm64: move thread_info off of the task stack Mark Rutland
2016-09-15 13:49 ` Mark Rutland
2016-09-15 13:49 ` Mark Rutland
2016-09-15 13:49 ` [kernel-hardening] [RFC PATCH 1/8] thread_info: include <current.h> for THREAD_INFO_IN_TASK Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49 ` [kernel-hardening] [RFC PATCH 2/8] thread_info: allow custom in-task thread_info Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 18:37   ` [kernel-hardening] " Andy Lutomirski
2016-09-15 18:37     ` Andy Lutomirski
2016-09-15 18:37     ` Andy Lutomirski
2016-09-16 10:33     ` [kernel-hardening] " Mark Rutland
2016-09-16 10:33       ` Mark Rutland
2016-09-16 10:33       ` Mark Rutland
2016-09-16 15:11       ` [kernel-hardening] " Andy Lutomirski
2016-09-16 15:11         ` Andy Lutomirski
2016-09-16 15:11         ` Andy Lutomirski
2016-09-19 10:44         ` [kernel-hardening] " Mark Rutland
2016-09-19 10:44           ` Mark Rutland
2016-09-19 10:44           ` Mark Rutland
2016-09-21 10:28         ` [kernel-hardening] " Mark Rutland
2016-09-21 10:28           ` Mark Rutland
2016-09-21 10:28           ` Mark Rutland
2016-09-22 22:23           ` [kernel-hardening] " Andy Lutomirski
2016-09-22 22:23             ` Andy Lutomirski
2016-09-22 22:23             ` Andy Lutomirski
2016-09-23 17:31             ` Mark Rutland [this message]
2016-09-23 17:31               ` Mark Rutland
2016-09-23 17:31               ` Mark Rutland
2016-09-15 13:49 ` [kernel-hardening] [RFC PATCH 3/8] arm64: thread_info remove stale items Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49 ` [kernel-hardening] [RFC PATCH 4/8] arm64: asm-offsets: remove unused definitions Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49 ` [kernel-hardening] [RFC PATCH 5/8] arm64: assembler: introduce ldr_this_cpu Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49 ` [kernel-hardening] [RFC PATCH 6/8] arm64: traps: use task_struct instead of thread_info Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49 ` [kernel-hardening] [RFC PATCH 7/8] arm64: move sp_el0 and tpidr_el1 into cpu_suspend_ctx Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49 ` [kernel-hardening] [RFC PATCH 8/8] arm64: split thread_info from task stack Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-15 13:49   ` Mark Rutland
2016-09-21  1:26 ` [kernel-hardening] Re: [RFC PATCH 0/8] arm64: move thread_info off of the " Laura Abbott
2016-09-21  1:26   ` Laura Abbott
2016-09-21  1:26   ` Laura Abbott
2016-09-21 10:31   ` [kernel-hardening] " Mark Rutland
2016-09-21 10:31     ` Mark Rutland
2016-09-21 10:31     ` Mark Rutland

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=20160923173143.GA29830@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=luto@amacapital.net \
    --cc=suzuki.poulose@arm.com \
    --cc=takahiro.akashi@linaro.org \
    --cc=will.deacon@arm.com \
    /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.