mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+8f9f411152c9539f4e59@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] [mm?] WARNING: bad unlock balance in __mm_populate
Date: Wed, 05 Mar 2025 04:39:04 -0800	[thread overview]
Message-ID: <67c845e8.050a0220.15b4b9.0021.GAE@google.com> (raw)
In-Reply-To: <tencent_39D0AED84CBEE7DC86D712DEC64CC9AFAE06@qq.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 __mm_populate

mm2: 00000000b2166d05, map held lock: 1, vma: 0000000029fbeeab, ret: -14, __get_user_pages
mm: 00000000b2166d05, vma: 0000000029fbeeab, mmap lock held: 1, locked: 0, ret: -14, mm addr is valid: 1, __mm_populate
================================================
WARNING: lock held when returning to user space!
6.14.0-rc4-syzkaller-ge056da87c780-dirty #0 Not tainted
------------------------------------------------
syz-executor198/8642 is leaving the kernel with locks still held!
1 lock held by syz-executor198/8642:
 #0: ffff0000d544a3d0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_lock include/linux/mmap_lock.h:190 [inline]
 #0: ffff0000d544a3d0 (&mm->mmap_lock){++++}-{4:4}, at: __mm_populate+0x1a0/0x590 mm/gup.c:2017


Tested on:

commit:         e056da87 Merge remote-tracking branch 'will/for-next/p..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=1377d7a0580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d6b7e15dc5b5e776
dashboard link: https://syzkaller.appspot.com/bug?extid=8f9f411152c9539f4e59
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
patch:          https://syzkaller.appspot.com/x/patch.diff?x=17448254580000


  reply	other threads:[~2025-03-05 12:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-02 17:15 syzbot
2025-03-04  1:38 ` Edward Adam Davis
2025-03-04  1:54   ` syzbot
2025-03-04  2:01 ` Edward Adam Davis
2025-03-04  2:22   ` syzbot
2025-03-04 12:25 ` Edward Adam Davis
2025-03-04 13:19   ` syzbot
2025-03-04 14:33 ` Edward Adam Davis
2025-03-04 15:09   ` syzbot
2025-03-05  0:55 ` Edward Adam Davis
2025-03-05  1:17   ` syzbot
2025-03-05 12:08 ` Edward Adam Davis
2025-03-05 12:39   ` syzbot [this message]
2025-03-05 13:45 ` Edward Adam Davis
2025-03-05 14:09   ` syzbot
2025-03-05 14:15 ` Edward Adam Davis
2025-03-05 15:22   ` syzbot
2025-03-06 12:52 ` Edward Adam Davis
2025-03-06 12:54   ` syzbot
2025-03-06 12:57 ` Edward Adam Davis
2025-03-06 13:24   ` syzbot
2025-03-09  3:30 ` Edward Adam Davis
2025-03-09  3:53   ` syzbot
2025-03-16  3:32 ` Edward Adam Davis
2025-03-16  4:29   ` 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=67c845e8.050a0220.15b4b9.0021.GAE@google.com \
    --to=syzbot+8f9f411152c9539f4e59@syzkaller.appspotmail.com \
    --cc=eadavis@qq.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 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®