linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@linux.intel.com>
To: Khalid Aziz <khalid.aziz@oracle.com>,
	akpm@linux-foundation.org, davem@davemloft.net
Cc: mhocko@suse.com, jack@suse.cz, kirill.shutemov@linux.intel.com,
	ross.zwisler@linux.intel.com, willy@infradead.org,
	hughd@google.com, n-horiguchi@ah.jp.nec.com, mgorman@suse.de,
	jglisse@redhat.com, dave.jiang@intel.com,
	dan.j.williams@intel.com, anthony.yznaga@oracle.com,
	nadav.amit@gmail.com, zi.yan@cs.rutgers.edu, aarcange@redhat.com,
	khandual@linux.vnet.ibm.com, aneesh.kumar@linux.vnet.ibm.com,
	henry.willard@oracle.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
	Khalid Aziz <khalid@gonehiking.org>
Subject: Re: [PATCH v12 08/11] mm: Clear arch specific VM flags on protection change
Date: Mon, 5 Mar 2018 11:23:27 -0800	[thread overview]
Message-ID: <df5344a2-f28d-7828-b76b-107dc24be2dd@linux.intel.com> (raw)
In-Reply-To: <f0bfc4b7ce6c8563bf0d5ef74af20b5d1edea66f.1519227112.git.khalid.aziz@oracle.com>

On 02/21/2018 09:15 AM, Khalid Aziz wrote:
> +/* Arch-specific flags to clear when updating VM flags on protection change */
> +#ifndef VM_ARCH_CLEAR
> +# define VM_ARCH_CLEAR	VM_NONE
> +#endif
> +#define VM_FLAGS_CLEAR	(ARCH_VM_PKEY_FLAGS | VM_ARCH_CLEAR)

Shouldn't this be defining

# define VM_ARCH_CLEAR	ARCH_VM_PKEY_FLAGS

on x86?

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2018-03-05 19:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 17:15 [PATCH v12 00/11] Application Data Integrity feature introduced by SPARC M7 Khalid Aziz
2018-02-21 17:15 ` [PATCH v12 02/11] mm, swap: Add infrastructure for saving page metadata on swap Khalid Aziz
2018-03-05 19:20   ` Dave Hansen
2018-03-05 19:29     ` Khalid Aziz
2018-03-05 19:35       ` Dave Hansen
2018-03-05 20:28         ` Khalid Aziz
2018-03-05 21:04           ` Dave Hansen
2018-03-05 21:14             ` Khalid Aziz
2018-03-06 22:47   ` Andrew Morton
2018-02-21 17:15 ` [PATCH v12 07/11] mm: Add address parameter to arch_validate_prot() Khalid Aziz
2018-02-26  5:54   ` Michael Ellerman
2018-03-06 22:48   ` Andrew Morton
2018-02-21 17:15 ` [PATCH v12 08/11] mm: Clear arch specific VM flags on protection change Khalid Aziz
2018-03-05 19:23   ` Dave Hansen [this message]
2018-03-05 20:38     ` Khalid Aziz
2018-03-06 22:48   ` Andrew Morton
2018-02-21 17:15 ` [PATCH v12 09/11] mm: Allow arch code to override copy_highpage() Khalid Aziz
2018-03-05 19:24   ` Dave Hansen
2018-03-05 20:42     ` Khalid Aziz
2018-03-05 20:56       ` Dave Hansen
2018-03-06 22:48   ` Andrew Morton
2018-02-21 17:15 ` [PATCH v12 10/11] sparc64: Add support for ADI (Application Data Integrity) Khalid Aziz
2018-02-23  2:50   ` kbuild test robot
2018-02-23 18:51     ` Khalid Aziz
2018-02-23 18:57       ` David Miller
2018-02-23 22:11         ` Khalid Aziz
2018-03-05 19:22   ` Dave Hansen
2018-03-05 21:14     ` Khalid Aziz
2018-03-05 21:26       ` Dave Hansen
2018-03-05 21:31       ` Dave Hansen
2018-03-05 22:55         ` Khalid Aziz
2018-03-05 21:26   ` Dave Hansen
2018-03-05 21:37     ` Khalid Aziz
2018-03-05 21:50       ` Dave Hansen
2018-03-18 15:08 ` [PATCH v12 00/11] Application Data Integrity feature introduced by SPARC M7 David Miller
2018-03-19 15:19   ` Khalid Aziz

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=df5344a2-f28d-7828-b76b-107dc24be2dd@linux.intel.com \
    --to=dave.hansen@linux.intel.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=anthony.yznaga@oracle.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=davem@davemloft.net \
    --cc=henry.willard@oracle.com \
    --cc=hughd@google.com \
    --cc=jack@suse.cz \
    --cc=jglisse@redhat.com \
    --cc=khalid.aziz@oracle.com \
    --cc=khalid@gonehiking.org \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.com \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=nadav.amit@gmail.com \
    --cc=ross.zwisler@linux.intel.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=willy@infradead.org \
    --cc=zi.yan@cs.rutgers.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).