From: syzbot <syzbot+29f7252ab8a82a688b5d@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, muchun.song@linux.dev,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [mm?] kernel BUG in resv_map_release (2)
Date: Sat, 13 Jul 2024 18:46:18 -0700 [thread overview]
Message-ID: <0000000000005ac71f061d2b4757@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 34afb82a3c67 Merge tag '6.10-rc6-smb3-server-fixes' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16ff8441980000
kernel config: https://syzkaller.appspot.com/x/.config?x=3456bae478301dc8
dashboard link: https://syzkaller.appspot.com/bug?extid=29f7252ab8a82a688b5d
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c2c5f697ee8f/disk-34afb82a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2aaaa729806e/vmlinux-34afb82a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3571e3d3b366/bzImage-34afb82a.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+29f7252ab8a82a688b5d@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at mm/hugetlb.c:1130!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 0 PID: 21140 Comm: syz.3.4250 Not tainted 6.10.0-rc7-syzkaller-00012-g34afb82a3c67 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:resv_map_release mm/hugetlb.c:1130 [inline]
RIP: 0010:resv_map_release+0x1f3/0x290 mm/hugetlb.c:1115
Code: a9 ff 48 85 db 75 1d e8 4b af a9 ff 48 8b 7c 24 08 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f e9 23 19 fb ff e8 2e af a9 ff 90 <0f> 0b 4c 89 ef e8 d3 72 05 00 e9 3d ff ff ff 48 89 ef e8 d6 71 05
RSP: 0018:ffffc90002d5f928 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffffffff81e4353b
RDX: ffff888029391e00 RSI: ffffffff81e43562 RDI: 0000000000000007
RBP: ffff88802e217860 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: ffff88802e217860
R13: ffff88802e217860 R14: ffff8880223b5e08 R15: dead000000000100
FS: 0000000000000000(0000) GS:ffff8880b9200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555587202808 CR3: 0000000069194000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
kref_put include/linux/kref.h:65 [inline]
hugetlb_vm_op_close+0x4ef/0x5d0 mm/hugetlb.c:5233
remove_vma+0x8b/0x180 mm/mmap.c:141
exit_mmap+0x4d4/0xb20 mm/mmap.c:3365
__mmput+0x12a/0x4d0 kernel/fork.c:1346
mmput+0x62/0x70 kernel/fork.c:1368
exit_mm kernel/exit.c:567 [inline]
do_exit+0x9b7/0x2ba0 kernel/exit.c:863
do_group_exit+0xd3/0x2a0 kernel/exit.c:1025
get_signal+0x2616/0x2710 kernel/signal.c:2909
arch_do_signal_or_restart+0x90/0x7e0 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0x14a/0x2a0 kernel/entry/common.c:218
do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1a21f75bd9
Code: Unable to access opcode bytes at 0x7f1a21f75baf.
RSP: 002b:00007f1a22c850f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007f1a22104040 RCX: 00007f1a21f75bd9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f1a22104040
RBP: 00007f1a22104038 R08: 00007f1a22c856c0 R09: 00007f1a22c856c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f1a22104044
R13: 000000000000006e R14: 00007ffd0fcf9b50 R15: 00007ffd0fcf9c38
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:resv_map_release mm/hugetlb.c:1130 [inline]
RIP: 0010:resv_map_release+0x1f3/0x290 mm/hugetlb.c:1115
Code: a9 ff 48 85 db 75 1d e8 4b af a9 ff 48 8b 7c 24 08 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f e9 23 19 fb ff e8 2e af a9 ff 90 <0f> 0b 4c 89 ef e8 d3 72 05 00 e9 3d ff ff ff 48 89 ef e8 d6 71 05
RSP: 0018:ffffc90002d5f928 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffffffff81e4353b
RDX: ffff888029391e00 RSI: ffffffff81e43562 RDI: 0000000000000007
RBP: ffff88802e217860 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: ffff88802e217860
R13: ffff88802e217860 R14: ffff8880223b5e08 R15: dead000000000100
FS: 0000000000000000(0000) GS:ffff8880b9200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020067000 CR3: 00000000669cc000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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:[~2024-07-14 1:46 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=0000000000005ac71f061d2b4757@google.com \
--to=syzbot+29f7252ab8a82a688b5d@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).