From: "Dae R. Jeong" <threeearcat@gmail.com>
To: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: kernel BUG in find_lock_entries
Date: Wed, 5 Apr 2023 19:52:45 +0900 [thread overview]
Message-ID: <ZC1S_f9nworAQpm_@dragonet> (raw)
Hi,
We observed an issue "kernel BUG in find_lock_entries". This was
observed a few months ago.
Unfortunately, we have not found a reproducer for the crash yet. We
will inform you if we have any update on this crash.
Detailed crash information is attached below.
Best regards,
Dae R. Jeong
-----
- Kernel version:
6.0-rc7
- Crash report:
------------[ cut here ]------------
kernel BUG at mm/filemap.c:2112!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 18497 Comm: syz-executor.0 Not tainted 6.0.0-rc7-00167-g92162e4a9862 #2
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
RIP: 0010:find_lock_entries+0xa93/0xaa0 mm/filemap.c:2111
Code: 4c 89 ef 48 c7 c6 c0 2a bc 8b e8 b8 ce 0e 00 0f 0b e8 71 99 a8 09 e8 4c 04 d3 ff 4c 89 ef 48 c7 c6 a0 1e bc 8b e8 9d ce 0e 00 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 90 55 48 89 e5 41 57 41 56 41
RSP: 0018:ffffc90009e0f9c0 EFLAGS: 00010246
RAX: 9de53b58cea03600 RBX: ffffea0000664dc0 RCX: 0000000000040000
RDX: ffffc90011e81000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffffc90009e0faf0 R08: ffffffff81e3af0a R09: ffffed1026b84f14
R10: ffffed1026b84f14 R11: 0000000000000000 R12: dffffc0000000000
R13: ffffea0000664dc0 R14: 00fff00000020015 R15: ffffc90009e0fa40
FS: 00007fa68d5be700(0000) GS:ffff888135c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056481d8d7317 CR3: 0000000018571000 CR4: 0000000000350ee0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
truncate_inode_pages_range+0x195/0x1120 mm/truncate.c:364
kill_bdev block/bdev.c:75 [inline]
set_blocksize+0x348/0x3c0 block/bdev.c:151
blkdev_bszset+0x202/0x2a0 block/ioctl.c:459
blkdev_ioctl+0x225/0x810 block/ioctl.c:597
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0x110/0x180 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4e/0xa0 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x4725fd
Code: 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa68d5bdbe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000057bf80 RCX: 00000000004725fd
RDX: 0000000020000080 RSI: 0000000040081271 RDI: 0000000000000005
RBP: 00000000f477909a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000057cbd8
R13: 000000000057bf8c R14: 00007ffddba46f90 R15: 00007fa68d5bdd80
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:find_lock_entries+0xa93/0xaa0 mm/filemap.c:2111
Code: 4c 89 ef 48 c7 c6 c0 2a bc 8b e8 b8 ce 0e 00 0f 0b e8 71 99 a8 09 e8 4c 04 d3 ff 4c 89 ef 48 c7 c6 a0 1e bc 8b e8 9d ce 0e 00 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 90 55 48 89 e5 41 57 41 56 41
RSP: 0018:ffffc90009e0f9c0 EFLAGS: 00010246
RAX: 9de53b58cea03600 RBX: ffffea0000664dc0 RCX: 0000000000040000
RDX: ffffc90011e81000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffffc90009e0faf0 R08: ffffffff81e3af0a R09: ffffed1026b84f14
R10: ffffed1026b84f14 R11: 0000000000000000 R12: dffffc0000000000
R13: ffffea0000664dc0 R14: 00fff00000020015 R15: ffffc90009e0fa40
FS: 00007fa68d5be700(0000) GS:ffff888135c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056481d8d7317 CR3: 0000000018571000 CR4: 0000000000350ee0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
next reply other threads:[~2023-04-05 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 10:52 Dae R. Jeong [this message]
2023-04-05 16:46 ` kernel BUG in find_lock_entries Jens Axboe
2023-04-05 22:25 ` Dae R. Jeong
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=ZC1S_f9nworAQpm_@dragonet \
--to=threeearcat@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.