[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180306144807.30915bcffe6e640c3ad6279c@linux-foundation.org>
Date: Tue, 6 Mar 2018 14:48:07 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Khalid Aziz <khalid.aziz@...cle.com>
Cc: benh@...nel.crashing.org, paulus@...ba.org, mpe@...erman.id.au,
davem@...emloft.net, dave.hansen@...ux.intel.com,
bsingharora@...il.com, nborisov@...e.com, aarcange@...hat.com,
anthony.yznaga@...cle.com, mgorman@...e.de, linuxram@...ibm.com,
kirill.shutemov@...ux.intel.com, dan.j.williams@...el.com,
jack@...e.cz, ross.zwisler@...ux.intel.com,
gregkh@...uxfoundation.org, tglx@...utronix.de, mhocko@...e.com,
n-horiguchi@...jp.nec.com, jglisse@...hat.com,
henry.willard@...cle.com, aneesh.kumar@...ux.vnet.ibm.com,
khandual@...ux.vnet.ibm.com, linuxppc-dev@...ts.ozlabs.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
sparclinux@...r.kernel.org, Khalid Aziz <khalid@...ehiking.org>
Subject: Re: [PATCH v12 07/11] mm: Add address parameter to
arch_validate_prot()
On Wed, 21 Feb 2018 10:15:49 -0700 Khalid Aziz <khalid.aziz@...cle.com> wrote:
> A protection flag may not be valid across entire address space and
> hence arch_validate_prot() might need the address a protection bit is
> being set on to ensure it is a valid protection flag. For example, sparc
> processors support memory corruption detection (as part of ADI feature)
> flag on memory addresses mapped on to physical RAM but not on PFN mapped
> pages or addresses mapped on to devices. This patch adds address to the
> parameters being passed to arch_validate_prot() so protection bits can
> be validated in the relevant context.
>
> Signed-off-by: Khalid Aziz <khalid.aziz@...cle.com>
> Cc: Khalid Aziz <khalid@...ehiking.org>
> Reviewed-by: Anthony Yznaga <anthony.yznaga@...cle.com>
Acked-by: Andrew Morton <akpm@...ux-foundation.org>
Powered by blists - more mailing lists