All of lore.kernel.org
 help / color / mirror / Atom feed
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 22:44:04 -0700	[thread overview]
Message-ID: <6870a4a4.a00a0220.26a83e.003c.GAE@google.com> (raw)
In-Reply-To: <20250711050913.3372-1-hdanton@sina.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING: lock held when returning to user space in lock_next_vma

================================================
WARNING: lock held when returning to user space!
6.16.0-rc5-next-20250710-syzkaller #0 Not tainted
------------------------------------------------
syz.0.21/6653 is leaving the kernel with locks still held!
2 locks held by syz.0.21/6653:
 #0: ffff8880722e3808 (vm_lock){++++}-{0:0}, at: lock_next_vma+0x146/0xdc0 mm/mmap_lock.c:220
 #1: ffff8880722e3308 (vm_lock){++++}-{0:0}, at: lock_next_vma+0x146/0xdc0 mm/mmap_lock.c:220


Tested on:

commit:         b551c4e2 Add linux-next specific files for 20250710
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15948d82580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=90b2e63e925474ab
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

Note: no patches were applied.

      reply	other threads:[~2025-07-11  5:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 17:52 [syzbot] [mm?] WARNING: lock held when returning to user space in lock_next_vma 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
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 [this message]

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=6870a4a4.a00a0220.26a83e.003c.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 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.