Re: [PATCH v2 0/2] Fix issues with vmalloc flush flag

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

To: "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "peterz@xxxxxxxxxxxxx" <peterz@xxxxxxxxxxxxx>, "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, "netdev@xxxxxxxxxxxxxxx" <netdev@xxxxxxxxxxxxxxx>, "sparclinux@xxxxxxxxxxxxxxx" <sparclinux@xxxxxxxxxxxxxxx>, "luto@xxxxxxxxxxxxxx" <luto@xxxxxxxxxxxxxx>
Subject: Re: [PATCH v2 0/2] Fix issues with vmalloc flush flag
From: "Edgecombe, Rick P" <rick.p.edgecombe@xxxxxxxxx>
Date: Mon, 20 May 2019 23:46:21 +0000
Accept-language: en-US
Cc: "davem@xxxxxxxxxxxxx" <davem@xxxxxxxxxxxxx>, "namit@xxxxxxxxxx" <namit@xxxxxxxxxx>, "Hansen, Dave" <dave.hansen@xxxxxxxxx>
In-reply-to: <20190520233841.17194-1-rick.p.edgecombe@intel.com>
References: <20190520233841.17194-1-rick.p.edgecombe@intel.com>
Thread-index: AQHVD2U2cXoGKMM3a0GhDqndH7zde6Z1IwAA
Thread-topic: [PATCH v2 0/2] Fix issues with vmalloc flush flag
User-agent: Evolution 3.30.1 (3.30.1-1.fc29)

On Mon, 2019-05-20 at 16:38 -0700, Rick Edgecombe wrote:
> These two patches address issues with the recently added
> VM_FLUSH_RESET_PERMS vmalloc flag. It is now split into two patches,
> which
> made sense to me, but can split it further if desired.
> 
Oops, this was supposed to say PATCH v3. Let me know if I should
resend.

References:
- [PATCH v2 0/2] Fix issues with vmalloc flush flag
  - From: Rick Edgecombe

Prev by Date: [PATCH v2 1/2] vmalloc: Fix calculation of direct map addr range
Next by Date: Re: [PATCH v2] vmalloc: Fix issues with flush flag
Previous by thread: [PATCH v2 1/2] vmalloc: Fix calculation of direct map addr range
Next by thread: [PATCH 1/2] open: add close_range()
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Development] [DCCP] [Linux ARM Development] [Linux] [Photo] [Yosemite Help] [Linux ARM Kernel] [Linux SCSI] [Linux x86_64] [Linux Hams]

Powered by Linux