From: Lance Yang <lance.yang@linux.dev>
To: syzbot ci <syzbot+ci5a676d3d210999ee@syzkaller.appspotmail.com>
Cc: syzbot@lists.linux.dev, osalvador@suse.de,
syzbot@syzkaller.appspotmail.com, linux-kernel@vger.kernel.org,
david@redhat.com, akpm@linux-foundation.org,
syzkaller-bugs@googlegroups.com, linux-mm@kvack.org,
muchun.song@linux.dev
Subject: Re: [syzbot ci] Re: mm/hugetlb: fix possible deadlock in __hugetlb_zap_begin
Date: Mon, 10 Nov 2025 17:31:48 +0800 [thread overview]
Message-ID: <b3f05987-74d9-4e6e-a18d-31e64c92337e@linux.dev> (raw)
In-Reply-To: <6911ad38.a70a0220.22f260.00dc.GAE@google.com>
On 2025/11/10 17:15, syzbot ci wrote:
> syzbot ci has tested the following series
>
> [v1] mm/hugetlb: fix possible deadlock in __hugetlb_zap_begin
> https://lore.kernel.org/all/20251110051421.29436-1-lance.yang@linux.dev
> * [PATCH 1/1] mm/hugetlb: fix possible deadlock in __hugetlb_zap_begin
>
> and found the following issues:
> * possible deadlock in move_hugetlb_page_tables
> * possible deadlock in remove_inode_hugepages
> * possible deadlock in unmap_vmas
Oops, this fix was incomplete, as other code paths with the reverse locking
order still exist, leading to the deadlocks reported by syzbot ...
Let me take a closer look ...
prev parent reply other threads:[~2025-11-10 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 5:14 [PATCH 1/1] " Lance Yang
2025-11-10 9:15 ` [syzbot ci] " syzbot ci
2025-11-10 9:31 ` Lance Yang [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=b3f05987-74d9-4e6e-a18d-31e64c92337e@linux.dev \
--to=lance.yang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=syzbot+ci5a676d3d210999ee@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzbot@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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