On Nov 7, 2022, at 11:27 AM, David Hildenbrand wrote:
> !! External Email
>
> On 07.11.22 20:03, Nadav Amit wrote:
>> On Nov 7, 2022, at 8:17 AM, David Hildenbrand wrote:
>>
>>> !! External Email
>>>
>>> Let's catch abuse of FAULT_FLAG_WR
On Nov 7, 2022, at 8:17 AM, David Hildenbrand wrote:
> !! External Email
>
> Let's catch abuse of FAULT_FLAG_WRITE early, such that we don't have to
> care in all other handlers and might get "surprises" if we forget to do
> so.
>
> Write faults without VM_MAYWRITE don't make any sense, and our
> On Nov 10, 2021, at 9:20 AM, Srivatsa S. Bhat wrote:
>
> On Tue, Nov 09, 2021 at 01:57:31PM -0800, Joe Perches wrote:
>> On Tue, 2021-11-09 at 00:58 +0000, Nadav Amit wrote:
>>>> On Nov 8, 2021, at 4:37 PM, Joe Perches wrote:
>>>> On Mon, 2021-11-08
> On Nov 8, 2021, at 4:37 PM, Joe Perches wrote:
>
> On Mon, 2021-11-08 at 16:22 -0800, Srivatsa S. Bhat wrote:
>
> So it's an exploder not an actual maintainer and it likely isn't
> publically archived with any normal list mechanism.
>
> So IMO "private" isn't appropriate. Neither is "L:"
discussion [1][2], it was recommended to
> mark them as such. Update all the remaining VMware mailing list
> references to use that format -- "L: list@address (private)”.
Acked-by: Nadav Amit
> On Jun 11, 2019, at 5:24 AM, Thomas Hellström (VMware)
> wrote:
>
> From: Thomas Hellstrom
>
[ snip ]
> +/**
> + * apply_pt_wrprotect - Leaf pte callback to write-protect a pte
> + * @pte: Pointer to the pte
> + * @token: Page table token, see apply_to_pfn_range()
> + * @addr: The virtual
> On Jun 11, 2019, at 2:20 PM, Thomas Hellström (VMware)
> wrote:
>
> On 6/11/19 9:10 PM, Nadav Amit wrote:
>>> On Jun 11, 2019, at 11:26 AM, Thomas Hellström (VMware)
>>> wrote:
>>>
>>> Hi, Nadav,
>>>
>>> On 6/11/19 7:
> On Jun 11, 2019, at 11:26 AM, Thomas Hellström (VMware)
> wrote:
>
> Hi, Nadav,
>
> On 6/11/19 7:21 PM, Nadav Amit wrote:
>>> On Jun 11, 2019, at 5:24 AM, Thomas Hellström (VMware)
>>> wrote:
>>>
>>> From: Thomas Hellstrom
>>
