All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f2577d8071a92e596253@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [mm?] WARNING in __gup_longterm_locked (2)
Date: Tue, 31 Oct 2023 14:28:31 -0700	[thread overview]
Message-ID: <0000000000001edf23060909d664@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    750b95887e56 Merge tag 'drm-fixes-2023-10-27' of git://ano..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=122bc757680000
kernel config:  https://syzkaller.appspot.com/x/.config?x=58203ba9e54216c8
dashboard link: https://syzkaller.appspot.com/bug?extid=f2577d8071a92e596253
compiler:       aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/384ffdcca292/non_bootable_disk-750b9588.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b80db9192f2c/vmlinux-750b9588.xz
kernel image: https://storage.googleapis.com/syzbot-assets/859893b5032c/Image-750b9588.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 29908 at mm/gup.c:1297 __get_user_pages+0x368/0x3ac mm/gup.c:1297
Modules linked in:
CPU: 1 PID: 29908 Comm: syz-executor.1 Not tainted 6.6.0-rc7-syzkaller-00137-g750b95887e56 #0
Hardware name: linux,dummy-virt (DT)
pstate: 81400009 (Nzcv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)
pc : __get_user_pages+0x368/0x3ac mm/gup.c:1297
lr : __get_user_pages+0x360/0x3ac mm/gup.c:1295
sp : ffff80008a2bbaa0
x29: ffff80008a2bbaa0 x28: 0000000000000000 x27: 0000000000080101
x26: 0000000000000000 x25: fdff000006a5ee40 x24: 00000000000001ff
x23: 0000000000000001 x22: 0000000000000000 x21: fdff000002c45540
x20: 0000000000000242 x19: 0000000020200700 x18: 0000000000000000
x17: 0000000000000000 x16: 0000000000000000 x15: 0000ffffc53b4698
x14: 000000000000018f x13: 0000000000000000 x12: ffff80008247fee8
x11: 0000000000000001 x10: 5479ecf2eae8e212 x9 : aa1a022e7ff96048
x8 : fdff000006a5fdc8 x7 : 0000000000000004 x6 : f9ff00002a61c000
x5 : 0000000000000000 x4 : fffffc0001f30000 x3 : 0000000000000002
x2 : 0000000000000007 x1 : fffffc0001f30034 x0 : 0000000000000000
Call trace:
 __get_user_pages+0x368/0x3ac mm/gup.c:1297
 __get_user_pages_locked mm/gup.c:1504 [inline]
 __gup_longterm_locked+0x1c0/0xa10 mm/gup.c:2203
 pin_user_pages+0x78/0xa0 mm/gup.c:3377
 io_pin_pages+0x74/0x118 io_uring/rsrc.c:1052
 io_sqe_buffer_register+0x70/0x424 io_uring/rsrc.c:1091
 io_sqe_buffers_register+0x118/0x268 io_uring/rsrc.c:1209
 __io_uring_register io_uring/io_uring.c:4429 [inline]
 __do_sys_io_uring_register io_uring/io_uring.c:4607 [inline]
 __se_sys_io_uring_register io_uring/io_uring.c:4567 [inline]
 __arm64_sys_io_uring_register+0xfc/0xdb8 io_uring/io_uring.c:4567
 __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline]
 invoke_syscall+0x48/0x114 arch/arm64/kernel/syscall.c:51
 el0_svc_common.constprop.0+0x40/0xe0 arch/arm64/kernel/syscall.c:136
 do_el0_svc+0x1c/0x28 arch/arm64/kernel/syscall.c:155
 el0_svc+0x40/0x114 arch/arm64/kernel/entry-common.c:678
 el0t_64_sync_handler+0x100/0x12c arch/arm64/kernel/entry-common.c:696
 el0t_64_sync+0x19c/0x1a0 arch/arm64/kernel/entry.S:595
---[ end trace 0000000000000000 ]---


---
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 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:[~2023-10-31 21:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0000000000001edf23060909d664@google.com \
    --to=syzbot+f2577d8071a92e596253@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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.