[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjxQpxK_vOpdcCycR2FGrSHLHZk+GVuVHrAv-8X3=XzUQ@mail.gmail.com>
Date: Wed, 2 Aug 2023 11:53:48 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: akpm@...ux-foundation.org, jannh@...gle.com, willy@...radead.org,
liam.howlett@...cle.com, david@...hat.com, peterx@...hat.com,
ldufour@...ux.ibm.com, vbabka@...e.cz, michel@...pinasse.org,
jglisse@...gle.com, mhocko@...e.com, hannes@...xchg.org,
dave@...olabs.net, hughd@...gle.com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, stable@...r.kernel.org
Subject: Re: [PATCH v2 4/6] mm: lock vma explicitly before doing
vm_flags_reset and vm_flags_reset_once
On Wed, 2 Aug 2023 at 11:09, Suren Baghdasaryan <surenb@...gle.com> wrote:
>
> Ok, IOW the vma would be already locked before mmap() is called...
Yup.
> Just to confirm, you are suggesting to remove vma_start_write() call
> from hfi1_file_mmap() and let vm_flags_reset() generate an assertion
> if it's ever called with an unlocked vma, correct?
Correct.
Linus
Powered by blists - more mailing lists