From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+a72c325b042aae6403c7@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [trace?] WARNING in tracing_buffers_mmap_close (2)
Date: Wed, 12 Nov 2025 07:27:26 +0800 [thread overview]
Message-ID: <20251111232728.9139-1-hdanton@sina.com> (raw)
In-Reply-To: <69136cdb.a70a0220.22f260.0142.GAE@google.com>
> Date: Tue, 11 Nov 2025 09:05:31 -0800
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 4a0c9b339199 Merge tag 'probes-fixes-v6.18-rc4' of git://g..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=127c3bcd980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=19d831c6d0386a9c
> dashboard link: https://syzkaller.appspot.com/bug?extid=a72c325b042aae6403c7
> compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13fb5342580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167c3bcd980000
#syz test
--- x/mm/mmap_lock.c
+++ y/mm/mmap_lock.c
@@ -240,6 +240,7 @@ retry:
/* Check if the VMA got isolated after we found it */
if (PTR_ERR(vma) == -EAGAIN) {
count_vm_vma_lock_event(VMA_LOCK_MISS);
+ mas_set(&mas, address);
/* The area was replaced with another one */
goto retry;
}
--
next prev parent reply other threads:[~2025-11-11 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 17:05 syzbot
2025-11-11 23:27 ` Hillf Danton [this message]
2025-11-11 23:44 ` syzbot
2025-11-19 5:51 ` Forwarded: [PATCH] tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs syzbot
2025-11-19 6:14 ` syzbot
[not found] <20251119055119.21473-1-kartikey406@gmail.com>
2025-11-19 6:15 ` [syzbot] [trace?] WARNING in tracing_buffers_mmap_close (2) syzbot
[not found] <20251119061356.25270-1-kartikey406@gmail.com>
2025-11-19 6:37 ` 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=20251111232728.9139-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+a72c325b042aae6403c7@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®