Re: [PATCH v1 1/1] mseal: update mseal.rst

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

To: jeffxu@xxxxxxxxxxxx
Subject: Re: [PATCH v1 1/1] mseal: update mseal.rst
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 27 Sep 2024 12:58:53 -0700
Cc: keescook@xxxxxxxxxxxx, corbet@xxxxxxx, jeffxu@xxxxxxxxxx, jorgelo@xxxxxxxxxxxx, groeck@xxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-kselftest@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, jannh@xxxxxxxxxx, sroettger@xxxxxxxxxx, pedro.falcato@xxxxxxxxx, linux-hardening@xxxxxxxxxxxxxxx, willy@xxxxxxxxxxxxx, gregkh@xxxxxxxxxxxxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx, deraadt@xxxxxxxxxxx, usama.anjum@xxxxxxxxxxxxx, surenb@xxxxxxxxxx, merimus@xxxxxxxxxx, rdunlap@xxxxxxxxxxxxx, lorenzo.stoakes@xxxxxxxxxx, Liam.Howlett@xxxxxxxxxx, enh@xxxxxxxxxx
In-reply-to: <20240927185211.729207-2-jeffxu@chromium.org>

On Fri, 27 Sep 2024 18:52:09 +0000 jeffxu@xxxxxxxxxxxx wrote:

> From: Jeff Xu <jeffxu@xxxxxxxxxxxx>
> 
> Update doc after in-loop change: mprotect/madvise can have
> partially updated and munmap is atomic.

Fixes:what?

I think 4a2dd02b0916 ("mm/mprotect: replace can_modify_mm with
can_modify_vma")?

Follow-Ups:
- Re: [PATCH v1 1/1] mseal: update mseal.rst
  - From: Jeff Xu

References:
- [PATCH v1 0/1] update mseal.rst
  - From: jeffxu
- [PATCH v1 1/1] mseal: update mseal.rst
  - From: jeffxu

Prev by Date: Re: [PATCH v2 04/19] iommufd: Allow pt_id to carry viommu_id for IOMMU_HWPT_ALLOC
Next by Date: Re: [PATCH v1 1/1] mseal: update mseal.rst
Previous by thread: [PATCH v1 1/1] mseal: update mseal.rst
Next by thread: Re: [PATCH v1 1/1] mseal: update mseal.rst
Index(es):
- Date
- Thread

[Index of Archives] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Share Photos] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Samba] [Device Mapper]