From: "Liam R. Howlett" <Liam.Howlett@Oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
maple-tree@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] More strict maple tree lockdep
Date: Fri, 14 Jul 2023 21:28:24 -0400 [thread overview]
Message-ID: <20230715012824.ihy6aagy3x7p4g43@revolver> (raw)
In-Reply-To: <CAHk-=wioXHeGOmMtLEAtx3enQ3TvtWudeAtK2bwoD0QyBN-GRw@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> [230714 16:16]:
> On Fri, 14 Jul 2023 at 12:56, Liam R. Howlett <Liam.Howlett@oracle.com> wrote:
> >
> > This series of patches adds checks to ensure the lock is held in write
> > mode during the write path of the maple tree instead of checking if it's
> > held at all.
>
> Ack, LGTM. I assume that there were no lockdep errors found by all this..
>
No lockdeps errors. My config has the additional CONFIG_PROVE_RCU=y
this time, which I missed during the previous locking changes.
Thanks,
Liam
prev parent reply other threads:[~2023-07-15 1:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 19:55 Liam R. Howlett
2023-07-14 19:55 ` [PATCH v2 1/4] mm/mmap: Clean up validate_mm() calls Liam R. Howlett
2023-07-14 19:55 ` [PATCH v2 2/4] maple_tree: Relax lockdep checks for on-stack trees Liam R. Howlett
2023-07-14 19:55 ` [PATCH v2 3/4] mm/mmap: Change detached vma locking scheme Liam R. Howlett
2023-07-19 18:31 ` Liam R. Howlett
2023-07-14 19:55 ` [PATCH v2 4/4] maple_tree: Be more strict about locking Liam R. Howlett
2023-07-14 20:15 ` [PATCH v2 0/4] More strict maple tree lockdep Linus Torvalds
2023-07-15 1:28 ` Liam R. Howlett [this message]
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=20230715012824.ihy6aagy3x7p4g43@revolver \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=torvalds@linux-foundation.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