Re: [PATCH 1/1] vmalloc: Fix issues with flush flag

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "netdev@xxxxxxxxxxxxxxx" <netdev@xxxxxxxxxxxxxxx>, "peterz@xxxxxxxxxxxxx" <peterz@xxxxxxxxxxxxx>, "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, "sparclinux@xxxxxxxxxxxxxxx" <sparclinux@xxxxxxxxxxxxxxx>, "bpf@xxxxxxxxxxxxxxx" <bpf@xxxxxxxxxxxxxxx>
Subject: Re: [PATCH 1/1] vmalloc: Fix issues with flush flag
From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
Date: Mon, 20 May 2019 19:13:48 +0000
Accept-language: en-US
Cc: "bp@xxxxxxxxx" <bp@xxxxxxxxx>, "davem@xxxxxxxxxxxxx" <davem@xxxxxxxxxxxxx>, "mroos@xxxxxxxx" <mroos@xxxxxxxx>, "luto@xxxxxxxxxx" <luto@xxxxxxxxxx>, "namit@xxxxxxxxxx" <namit@xxxxxxxxxx>, "Hansen, Dave" <dave.hansen@xxxxxxxxx>, "mingo@xxxxxxxxxx" <mingo@xxxxxxxxxx>
In-reply-to: <20190517210123.5702-2-rick.p.edgecombe@intel.com>
References: <20190517210123.5702-1-rick.p.edgecombe@intel.com> <20190517210123.5702-2-rick.p.edgecombe@intel.com>
User-agent: Evolution 3.30.1 (3.30.1-1.fc29)

On Fri, 2019-05-17 at 14:01 -0700, Rick Edgecomb e wrote:
> Meelis Roos reported issues with the new VM_FLUSH_RESET_PERMS flag on
> the
> sparc architecture.
> 
Argh, this patch is not correct in the flush range for non-x86. I'll
send a revision.

References:
- [PATCH 0/1] Fix for VM_FLUSH_RESET_PERMS on sparc
  - From: Rick Edgecombe
- [PATCH 1/1] vmalloc: Fix issues with flush flag
  - From: Rick Edgecombe

Prev by Date: Re: [PATCH] mm/dev_pfn: Exclude MEMORY_DEVICE_PRIVATE while computing virtual address
Next by Date: Re: [PATCH] mm/dev_pfn: Exclude MEMORY_DEVICE_PRIVATE while computing virtual address
Previous by thread: Re: [PATCH 1/1] vmalloc: Fix issues with flush flag
Next by thread: [v6 0/3] "Hotremove" persistent memory
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]