From: Andrew Morton <akpm@linux-foundation.org>
To: syzbot <syzbot+d4316c39e84f412115c9@syzkaller.appspotmail.com>
Cc: andrii@kernel.org, david@redhat.com, hdanton@sina.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
lorenzo.stoakes@oracle.com, surenb@google.com,
syzkaller-bugs@googlegroups.com, linux-mm@kvack.org
Subject: Re: [syzbot] [fs?] WARNING: bad unlock balance in query_matching_vma
Date: Tue, 15 Jul 2025 17:08:52 -0700 [thread overview]
Message-ID: <20250715170852.e616b82a53a88e757ee342af@linux-foundation.org> (raw)
In-Reply-To: <687628be.a00a0220.3af5df.0002.GAE@google.com>
On Tue, 15 Jul 2025 03:09:02 -0700 syzbot <syzbot+d4316c39e84f412115c9@syzkaller.appspotmail.com> wrote:
> syzbot has bisected this issue to:
>
> commit fb8a9ee1f05345b1fae37902d32d954d2150437b
> Author: Suren Baghdasaryan <surenb@google.com>
> Date: Fri Jul 4 06:07:26 2025 +0000
>
> fs/proc/task_mmu: execute PROCMAP_QUERY ioctl under per-vma locks
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=171c27d4580000
> start commit: a62b7a37e6fc Add linux-next specific files for 20250711
> git tree: linux-next
> final oops: https://syzkaller.appspot.com/x/report.txt?x=149c27d4580000
> console output: https://syzkaller.appspot.com/x/log.txt?x=109c27d4580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=bb4e3ec360fcbd0f
> dashboard link: https://syzkaller.appspot.com/bug?extid=d4316c39e84f412115c9
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14ad50f0580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1173018c580000
>
> Reported-by: syzbot+d4316c39e84f412115c9@syzkaller.appspotmail.com
Thanks.
This email (and the original bug report) lacked a cc:linux-mm@kvack.org.
> Fixes: fb8a9ee1f053 ("fs/proc/task_mmu: execute PROCMAP_QUERY ioctl under per-vma locks")
Could I suggest that your scripts be altered to parse the fb8a9ee1f053
changelog for its Link:, fetch the submitter's original email and from
that, figure out which mailing list(s) were cc'ed?
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Suren, I'll drop the v6 series from mm-new. Links which I have
accumulated are:
https://lkml.kernel.org/r/6871f94b.a00a0220.26a83e.0070.GAE@google.com
https://lkml.kernel.org/r/f532558b-b19a-40ea-b594-94d1ba92188d@lucifer.local
https://lkml.kernel.org/r/687628be.a00a0220.3af5df.0002.GAE@google.com
https://lkml.kernel.org/r/687628be.a00a0220.3af5df.0002.GAE@google.com
parent reply other threads:[~2025-07-16 0:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <687628be.a00a0220.3af5df.0002.GAE@google.com>]
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=20250715170852.e616b82a53a88e757ee342af@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=david@redhat.com \
--cc=hdanton@sina.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=surenb@google.com \
--cc=syzbot+d4316c39e84f412115c9@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