From: syzbot <syzbot+80011ad33eec39e6ce42@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING: lock held when returning to user space in lock_next_vma
Date: Thu, 10 Jul 2025 20:56:02 -0700 [thread overview]
Message-ID: <68708b52.a00a0220.26a83e.0034.GAE@google.com> (raw)
In-Reply-To: <20250711035418.3336-1-hdanton@sina.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to checkout kernel repo https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master: failed to run ["git" "fetch" "--force" "c7d0fbf060793662bad7a58c248d99da187d8f14" "master"]: exit status 128
fatal: repository 'https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/' not found
Tested on:
commit: [unknown
git tree: https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
kernel config: https://syzkaller.appspot.com/x/.config?x=1e4f88512ae53408
dashboard link: https://syzkaller.appspot.com/bug?extid=80011ad33eec39e6ce42
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=16b0ba8c580000
next prev parent reply other threads:[~2025-07-11 3:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 17:52 syzbot
2025-07-08 22:19 ` Suren Baghdasaryan
2025-07-08 23:15 ` Liam R. Howlett
2025-07-08 23:51 ` Suren Baghdasaryan
2025-07-09 0:05 ` Suren Baghdasaryan
2025-07-09 10:26 ` Vlastimil Babka
2025-07-09 14:29 ` Suren Baghdasaryan
2025-07-09 1:54 ` syzbot
2025-07-11 0:32 ` Hillf Danton
2025-07-11 1:25 ` syzbot
2025-07-11 2:25 ` Hillf Danton
2025-07-11 2:30 ` syzbot
2025-07-11 3:54 ` Hillf Danton
2025-07-11 3:56 ` syzbot [this message]
2025-07-11 4:03 ` Hillf Danton
2025-07-11 4:28 ` syzbot
2025-07-11 5:09 ` Hillf Danton
2025-07-11 5:44 ` syzbot
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=68708b52.a00a0220.26a83e.0034.GAE@google.com \
--to=syzbot+80011ad33eec39e6ce42@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--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®