All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+80011ad33eec39e6ce42@syzkaller.appspotmail.com>
To: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
	 linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	lorenzo.stoakes@oracle.com,  shakeel.butt@linux.dev,
	surenb@google.com, syzkaller-bugs@googlegroups.com,
	 vbabka@suse.cz
Subject: [syzbot] [mm?] WARNING: lock held when returning to user space in lock_next_vma
Date: Tue, 08 Jul 2025 10:52:27 -0700	[thread overview]
Message-ID: <686d5adb.050a0220.1ffab7.0019.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    26ffb3d6f02c Add linux-next specific files for 20250704
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1719df70580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1e4f88512ae53408
dashboard link: https://syzkaller.appspot.com/bug?extid=80011ad33eec39e6ce42
compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1124abd4580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1099df70580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fd5569903143/disk-26ffb3d6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1b0c9505c543/vmlinux-26ffb3d6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9d864c72bed1/bzImage-26ffb3d6.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+80011ad33eec39e6ce42@syzkaller.appspotmail.com

================================================
WARNING: lock held when returning to user space!
6.16.0-rc4-next-20250704-syzkaller #0 Not tainted
------------------------------------------------
syz.0.22/6068 is leaving the kernel with locks still held!
1 lock held by syz.0.22/6068:
 #0: ffff8880792a3588 (vm_lock){++++}-{0:0}, at: lock_next_vma+0x146/0xdc0 mm/mmap_lock.c:220


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup


             reply	other threads:[~2025-07-08 17:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 17:52 syzbot [this message]
2025-07-08 22:19 ` [syzbot] [mm?] WARNING: lock held when returning to user space in lock_next_vma 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
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=686d5adb.050a0220.1ffab7.0019.GAE@google.com \
    --to=syzbot+80011ad33eec39e6ce42@syzkaller.appspotmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=shakeel.butt@linux.dev \
    --cc=surenb@google.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.