From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+c473aa669b5e8a6f48d2@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] possible deadlock in mfill_get_vma
Date: Mon, 16 Mar 2026 09:19:18 +0800 [thread overview]
Message-ID: <20260316011919.998-1-hdanton@sina.com> (raw)
In-Reply-To: <69b6fc68.a00a0220.3b25d1.001e.GAE@google.com>
> Date: Sun, 15 Mar 2026 11:37:28 -0700 [thread overview]
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: b84a0ebe421c Add linux-next specific files for 20260313
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=131ab8da580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=e7280ad1f68b2dce
> dashboard link: https://syzkaller.appspot.com/bug?extid=c473aa669b5e8a6f48d2
> compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=126c98ba580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1644a2d6580000
#syz test
--- x/mm/userfaultfd.c
+++ y/mm/userfaultfd.c
@@ -217,6 +217,7 @@ static int mfill_get_vma(struct mfill_st
dst_vma = uffd_mfill_lock(ctx->mm, state->dst_start, state->len);
if (IS_ERR(dst_vma))
return PTR_ERR(dst_vma);
+ state->vma = dst_vma;
/*
* If memory mappings are changing because of non-cooperative
--
next prev parent reply other threads:[~2026-03-16 1:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 18:37 syzbot
2026-03-16 0:57 ` Edward Adam Davis
2026-03-16 1:35 ` syzbot
2026-03-16 1:19 ` Hillf Danton [this message]
2026-03-16 1:56 ` syzbot
2026-03-16 1:49 ` Edward Adam Davis
2026-03-16 2:20 ` syzbot
2026-03-16 2:21 ` Edward Adam Davis
2026-03-16 3:07 ` syzbot
2026-03-16 3:11 ` [PATCH next] userfaultfd: unassigned vma leads to a potential unreleased locks Edward Adam Davis
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=20260316011919.998-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+c473aa669b5e8a6f48d2@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
all inboxes | Powered by JetHome®