[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <861682210.23281.1709809857201.JavaMail.zimbra@nod.at>
Date: Thu, 7 Mar 2024 12:10:57 +0100 (CET)
From: Richard Weinberger <richard@....at>
To: David Hildenbrand <david@...hat.com>
Cc: linux-mm <linux-mm@...ck.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
upstream+pagemap@...ma-star.at, adobriyan@...il.com,
wangkefeng wang <wangkefeng.wang@...wei.com>,
ryan roberts <ryan.roberts@....com>, hughd@...gle.com,
peterx@...hat.com, avagin@...gle.com, lstoakes@...il.com,
vbabka <vbabka@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>,
usama anjum <usama.anjum@...labora.com>,
Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH 2/2] [RFC] pagemap.rst: Document write bit
----- Ursprüngliche Mail -----
> Von: "David Hildenbrand" <david@...hat.com>
> An: "richard" <richard@....at>, "linux-mm" <linux-mm@...ck.org>
>> + Bit 58 is useful to detect CoW mappings; however, it does not indicate
>> + whether the page mapping is writable or not. If an anonymous mapping is
>> + writable but the write bit is not set, it means that the next write access
>> + will cause a page fault, and copy-on-write will happen.
>
> That is not true.
Can you please help me correct my obvious misunderstanding?
Powered by blists - more mailing lists