All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Laura Abbott <labbott@redhat.com>
Cc: AKASHI Takahiro <takahiro.akashi@linaro.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	David Brown <david.brown@linaro.org>,
	Will Deacon <will.deacon@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
	kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] Re: [PATCHv2 2/4] arm64: dump: Make the page table dumping seq_file optional
Date: Mon, 17 Oct 2016 12:02:30 +0100	[thread overview]
Message-ID: <20161017110229.GC29095@leverpostej> (raw)
In-Reply-To: <1476311522-15381-3-git-send-email-labbott@redhat.com>

On Wed, Oct 12, 2016 at 03:32:00PM -0700, Laura Abbott wrote:
> 
> The page table dumping code always assumes it will be dumping to a
> seq_file to userspace. Future code will be taking advantage of
> the page table dumping code but will not need the seq_file. Make
> the seq_file optional for these cases.
> 
> Acked-by: Mark Rutland <mark.rutland@arm.com>

Now that I'm back in the office with access to hardware, I've been able
to give this a spin. FWIW, feel free to upgrade the above to:

Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Tested-by: Mark Rutland <mark.rutland@arm.com>

Thanks,
Mark.

WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 2/4] arm64: dump: Make the page table dumping seq_file optional
Date: Mon, 17 Oct 2016 12:02:30 +0100	[thread overview]
Message-ID: <20161017110229.GC29095@leverpostej> (raw)
In-Reply-To: <1476311522-15381-3-git-send-email-labbott@redhat.com>

On Wed, Oct 12, 2016 at 03:32:00PM -0700, Laura Abbott wrote:
> 
> The page table dumping code always assumes it will be dumping to a
> seq_file to userspace. Future code will be taking advantage of
> the page table dumping code but will not need the seq_file. Make
> the seq_file optional for these cases.
> 
> Acked-by: Mark Rutland <mark.rutland@arm.com>

Now that I'm back in the office with access to hardware, I've been able
to give this a spin. FWIW, feel free to upgrade the above to:

Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Tested-by: Mark Rutland <mark.rutland@arm.com>

Thanks,
Mark.

WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: Laura Abbott <labbott@redhat.com>
Cc: AKASHI Takahiro <takahiro.akashi@linaro.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	David Brown <david.brown@linaro.org>,
	Will Deacon <will.deacon@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
	kernel-hardening@lists.openwall.com
Subject: Re: [PATCHv2 2/4] arm64: dump: Make the page table dumping seq_file optional
Date: Mon, 17 Oct 2016 12:02:30 +0100	[thread overview]
Message-ID: <20161017110229.GC29095@leverpostej> (raw)
In-Reply-To: <1476311522-15381-3-git-send-email-labbott@redhat.com>

On Wed, Oct 12, 2016 at 03:32:00PM -0700, Laura Abbott wrote:
> 
> The page table dumping code always assumes it will be dumping to a
> seq_file to userspace. Future code will be taking advantage of
> the page table dumping code but will not need the seq_file. Make
> the seq_file optional for these cases.
> 
> Acked-by: Mark Rutland <mark.rutland@arm.com>

Now that I'm back in the office with access to hardware, I've been able
to give this a spin. FWIW, feel free to upgrade the above to:

Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Tested-by: Mark Rutland <mark.rutland@arm.com>

Thanks,
Mark.

  reply	other threads:[~2016-10-17 11:02 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 22:31 [kernel-hardening] [PATCHv2 0/4] WX checking for arm64 Laura Abbott
2016-10-12 22:31 ` Laura Abbott
2016-10-12 22:31 ` Laura Abbott
2016-10-12 22:31 ` [kernel-hardening] [PATCHv2 1/4] arm64: dump: Make ptdump debugfs a separate option Laura Abbott
2016-10-12 22:31   ` Laura Abbott
2016-10-12 22:31   ` Laura Abbott
2016-10-12 22:45   ` [kernel-hardening] " Kees Cook
2016-10-12 22:45     ` Kees Cook
2016-10-12 22:45     ` Kees Cook
2016-10-12 22:57     ` [kernel-hardening] " Laura Abbott
2016-10-12 22:57       ` Laura Abbott
2016-10-12 22:57       ` Laura Abbott
2016-10-12 23:13       ` [kernel-hardening] " Kees Cook
2016-10-12 23:13         ` Kees Cook
2016-10-12 23:13         ` Kees Cook
2016-10-17 10:52   ` [kernel-hardening] " Mark Rutland
2016-10-17 10:52     ` Mark Rutland
2016-10-17 10:52     ` Mark Rutland
2016-10-17 22:16     ` [kernel-hardening] " Laura Abbott
2016-10-17 22:16       ` Laura Abbott
2016-10-17 22:16       ` Laura Abbott
2016-10-12 22:32 ` [kernel-hardening] [PATCHv2 2/4] arm64: dump: Make the page table dumping seq_file optional Laura Abbott
2016-10-12 22:32   ` Laura Abbott
2016-10-12 22:32   ` Laura Abbott
2016-10-17 11:02   ` Mark Rutland [this message]
2016-10-17 11:02     ` Mark Rutland
2016-10-17 11:02     ` Mark Rutland
2016-10-12 22:32 ` [kernel-hardening] [PATCHv2 3/4] arm64: dump: Remove max_addr Laura Abbott
2016-10-12 22:32   ` Laura Abbott
2016-10-12 22:32   ` Laura Abbott
2016-10-17 11:05   ` [kernel-hardening] " Mark Rutland
2016-10-17 11:05     ` Mark Rutland
2016-10-17 11:05     ` Mark Rutland
2016-10-12 22:32 ` [kernel-hardening] [PATCHv2 4/4] arm64: dump: Add checking for writable and exectuable pages Laura Abbott
2016-10-12 22:32   ` Laura Abbott
2016-10-12 22:32   ` Laura Abbott
2016-10-17 12:47   ` [kernel-hardening] " Mark Rutland
2016-10-17 12:47     ` Mark Rutland
2016-10-17 12:47     ` 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=20161017110229.GC29095@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=david.brown@linaro.org \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=labbott@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.