linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Matthew Wilcox <willy@infradead.org>,
	Mike Rapoport <rppt@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Suren Baghdasaryan <surenb@google.com>,
	linux-doc@vger.kernel.org
Subject: Re: [RFC PATCH] docs/mm: add VMA locks documentation
Date: Tue, 5 Nov 2024 14:18:01 +0000	[thread overview]
Message-ID: <441f3ae8-1e8a-42be-9f65-54ccf58e3fa3@lucifer.local> (raw)
In-Reply-To: <CAH5fLggpEezhR_o+8RPmYix-JLZ47HwQLQM2OUzKQg3i7UYu5Q@mail.gmail.com>

On Tue, Nov 05, 2024 at 02:56:43PM +0100, Alice Ryhl wrote:
[snip]
> >
> > As a wordy aside, a large part of the motivation of this document, or
> > certainly my prioritisation of it, is explicitly to help the rust team
> > correctly abstract this aspect of mm.
> >
> > The other part is to help the mm team, that is especailly myself, correctly
> > understand and _remember_ the numerous painful ins and outs of this stuff,
> > much of which has been pertinent of late for not wonderfully positive
> > reasons.
> >
> > Hopefully we accomplish both! :>)
>
> I do think this has revealed one issue with my Rust patch, which is
> that VmAreaMut currently requires the mmap lock, but it should also
> require the vma lock, since you need both for writing.
>
> Alice

Awesome :) I am genuinely hoping this doc will aid you guys in rust in
general.

And maybe I can use advent of code this year to actually learn the language
myself...

I nominate Vlasta to join me ;)


  reply	other threads:[~2024-11-05 14:18 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 18:50 Lorenzo Stoakes
2024-11-01 20:58 ` Lorenzo Stoakes
2024-11-01 22:41   ` Suren Baghdasaryan
2024-11-01 23:48   ` SeongJae Park
2024-11-04 13:02     ` Lorenzo Stoakes
2024-11-04 13:47       ` Mike Rapoport
2024-11-04 19:55         ` Lorenzo Stoakes
2024-11-02  1:45 ` Jann Horn
2024-11-04 16:42   ` Lorenzo Stoakes
2024-11-04 21:29     ` Jann Horn
2024-11-05 16:10       ` Lorenzo Stoakes
2024-11-05 17:21         ` Jann Horn
2024-11-06  3:09       ` Qi Zheng
2024-11-06 18:09         ` Jann Horn
2024-11-07  7:07           ` Qi Zheng
2024-11-06  2:56     ` Qi Zheng
2024-11-06 11:28       ` Lorenzo Stoakes
2024-11-07  6:47         ` Qi Zheng
2024-11-02  9:00 ` Mike Rapoport
2024-11-04 14:17   ` Lorenzo Stoakes
2024-11-04 15:19     ` Mike Rapoport
2024-11-05 12:23       ` Lorenzo Stoakes
2024-11-04 14:47 ` Alice Ryhl
2024-11-04 16:52   ` Lorenzo Stoakes
2024-11-05 13:56     ` Alice Ryhl
2024-11-05 14:18       ` Lorenzo Stoakes [this message]
2024-11-04 17:01 ` Suren Baghdasaryan
2024-11-04 21:04   ` Lorenzo Stoakes
2024-11-04 21:20     ` Suren Baghdasaryan
2024-11-05 16:11       ` Lorenzo Stoakes
2024-11-04 21:25     ` Jann Horn
2024-11-07 11:07 ` Hillf Danton
2024-11-07 11:15   ` 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=441f3ae8-1e8a-42be-9f65-54ccf58e3fa3@lucifer.local \
    --to=lorenzo.stoakes@oracle.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=aliceryhl@google.com \
    --cc=boqun.feng@gmail.com \
    --cc=corbet@lwn.net \
    --cc=jannh@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rppt@kernel.org \
    --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