linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	linux-man@vger.kernel.org, Suren Baghdasaryan <surenb@google.com>,
	"Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Matthew Wilcox <willy@infradead.org>,
	Jann Horn <jannh@google.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH man-pages v4] madvise.2: add MADV_GUARD_INSTALL, MADV_GUARD_REMOVE description
Date: Thu, 5 Dec 2024 23:53:02 +0100	[thread overview]
Message-ID: <20241205225302.xbvfws6y37zlt5ba@devuan> (raw)
In-Reply-To: <01514d6a-5b8f-4a38-8c08-7cacede47f67@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]

Hi Vlastimil, Lorenzo,

On Thu, Dec 05, 2024 at 09:43:09PM +0100, Vlastimil Babka wrote:
> >> > +If the region maps memory pages they will be cleared as part of the operation,
> >> > +though if
> >>
> >> Hm this reads a bit ambiguous. One could read it as the memory pages are
> >> being cleared, but it's the page tables.
> > 
> > This was really hard to word, because you don't want to say unmapped, and saying
> > 'clearing page tables' or 'zapping' is clear to us but not necessarily to a
> > reader. 'Clearing mapping' makes it ambiguous vs. munmap(), etc. etc.
> 
> Maybe saying "removed" instead of "cleared" would be better?
> 
> Anyway, I don't want to cause bikeshedding, so in any case:

I would actually like you to bikeshed.  :-)
These wording issues tend to be important, and finding the right wording
is worth the bikeshedding.

On the other hand, sometimes we just don't have ideas, and merging and
later fixing is also okay.

> 
> Reviewed-by: Vlastimil Babka <vbabka@suse.cz>

Thanks!

Have a lovely night!
Alex

> 
> > But you want to make it clear (no pun intended) that anon pages, if there's any
> > data, it's probably lost. So I think this is a distinction that doesn't matter.
> > 
> > Will revisit once we support file-backed mappings.
> > 
> 

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-12-05 22:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05 10:41 Lorenzo Stoakes
2024-12-05 12:20 ` Alejandro Colomar
2024-12-05 12:26   ` Lorenzo Stoakes
2024-12-05 12:43     ` git repositories and branches (was: [PATCH man-pages v4] madvise.2: ...) Alejandro Colomar
2024-12-05 13:06       ` Lorenzo Stoakes
2024-12-05 17:50 ` [PATCH man-pages v4] madvise.2: add MADV_GUARD_INSTALL, MADV_GUARD_REMOVE description Vlastimil Babka
2024-12-05 18:09   ` Lorenzo Stoakes
2024-12-05 20:43     ` Vlastimil Babka
2024-12-05 22:53       ` Alejandro Colomar [this message]
2024-12-06 11:03       ` Lorenzo Stoakes
2024-12-06 11:22         ` Lorenzo Stoakes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241205225302.xbvfws6y37zlt5ba@devuan \
    --to=alx@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=jannh@google.com \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox