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,
	andrii@kernel.org,  anna.luese@v-bien.de,
	liam.howlett@oracle.com, 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: Re: [syzbot] [mm?] WARNING: lock held when returning to user space in lock_next_vma
Date: Tue, 08 Jul 2025 18:54:03 -0700	[thread overview]
Message-ID: <686dcbbb.050a0220.1ffab7.002a.GAE@google.com> (raw)
In-Reply-To: <686d5adb.050a0220.1ffab7.0019.GAE@google.com>

syzbot has bisected this issue to:

commit 6772c457a86536f3496bf5b3716f34a5ac125783
Author: Suren Baghdasaryan <surenb@google.com>
Date:   Tue Jun 24 19:33:59 2025 +0000

    fs/proc/task_mmu:: execute PROCMAP_QUERY ioctl under per-vma locks

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=158fca8c580000
start commit:   26ffb3d6f02c Add linux-next specific files for 20250704
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=178fca8c580000
console output: https://syzkaller.appspot.com/x/log.txt?x=138fca8c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1e4f88512ae53408
dashboard link: https://syzkaller.appspot.com/bug?extid=80011ad33eec39e6ce42
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1124abd4580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1099df70580000

Reported-by: syzbot+80011ad33eec39e6ce42@syzkaller.appspotmail.com
Fixes: 6772c457a865 ("fs/proc/task_mmu:: execute PROCMAP_QUERY ioctl under per-vma locks")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection


  parent reply	other threads:[~2025-07-09  1:54 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 [this message]
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=686dcbbb.050a0220.1ffab7.002a.GAE@google.com \
    --to=syzbot+80011ad33eec39e6ce42@syzkaller.appspotmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrii@kernel.org \
    --cc=anna.luese@v-bien.de \
    --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.