From: Jens Axboe <axboe@kernel.dk>
To: Uladzislau Rezki <urezki@gmail.com>, Omar Sandoval <osandov@osandov.com>
Cc: Linux-MM <linux-mm@kvack.org>, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: vmalloc: annotate find_vmap_area_exceed_addr_lock() for lockdep
Date: Wed, 27 Mar 2024 11:21:59 -0600 [thread overview]
Message-ID: <b436feed-610f-4165-884e-9c2b015c0027@kernel.dk> (raw)
In-Reply-To: <ZgRRuxJy8cs-FTmb@pc638.lan>
On 3/27/24 11:04 AM, Uladzislau Rezki wrote:
> Hello, Jens, Omar!
>
>> On Tue, Mar 26, 2024 at 04:24:01PM -0600, Jens Axboe wrote:
>>> On 3/26/24 3:25 PM, Jens Axboe wrote:
>>>> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
>>>> index 22aa63f4ef63..26a69fa6809c 100644
>>>> --- a/mm/vmalloc.c
>>>> +++ b/mm/vmalloc.c
>>>> @@ -1032,7 +1032,7 @@ find_vmap_area_exceed_addr_lock(unsigned long addr, struct vmap_area **va)
>>>> for (i = 0; i < nr_vmap_nodes; i++) {
>>>> vn = &vmap_nodes[i];
>>>>
>>>> - spin_lock(&vn->busy.lock);
>>>> + spin_lock_nested(&vn->busy.lock, i);
>>>> va_lowest = __find_vmap_area_exceed_addr(addr, &vn->busy.root);
>>>> if (va_lowest) {
>>>> if (!va_node || va_lowest->va_start < (*va)->va_start) {
>>>
>>> Omar said he tested this and ran into lockdep complaining as it only
>>> supports 8 subclasses. So this patch can't work, but that still leaves
>>> the current kernel code buggy...
>>>
>> It is a bit tricky. Let me rewrite it so a lockdep does not complain.
>>
>> Thank you for your report.
>>
>
> Could you please check and test below? It is based on latest 6.9-rc1 tip.
> I have reworked it a bit and now it does not hold two locks so the lockdep
> should not complain.
Works for me:
Tested-by: Jens Axboe <axboe@kernel.dk>
--
Jens Axboe
next prev parent reply other threads:[~2024-03-27 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 21:25 Jens Axboe
2024-03-26 22:24 ` Jens Axboe
2024-03-27 9:57 ` Uladzislau Rezki
2024-03-27 17:04 ` Uladzislau Rezki
2024-03-27 17:21 ` Jens Axboe [this message]
2024-03-27 17:40 ` Uladzislau Rezki
2024-03-27 17:22 ` Omar Sandoval
2024-03-27 17:41 ` Uladzislau Rezki
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=b436feed-610f-4165-884e-9c2b015c0027@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=osandov@osandov.com \
--cc=urezki@gmail.com \
/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