From: syzbot <syzbot+6b74cf8fcd7378d8be7c@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: [syzbot] BUG: unable to handle kernel paging request in evict
Date: Sat, 24 Sep 2022 16:36:01 -0700 [thread overview]
Message-ID: <000000000000e4630c05e974c1eb@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 200e340f2196 Merge tag 'pull-work.dcache' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=163e7eb6080000
kernel config: https://syzkaller.appspot.com/x/.config?x=a3f4d6985d3164cd
dashboard link: https://syzkaller.appspot.com/bug?extid=6b74cf8fcd7378d8be7c
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6b74cf8fcd7378d8be7c@syzkaller.appspotmail.com
BUG: unable to handle page fault for address: ffffffffffffffc8
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD ba8f067 P4D ba8f067 PUD ba91067 PMD 0
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 10298 Comm: syz-executor.4 Not tainted 5.19.0-syzkaller-02972-g200e340f2196 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:lock_acquire kernel/locking/lockdep.c:5666 [inline]
RIP: 0010:lock_acquire+0x1aa/0x570 kernel/locking/lockdep.c:5631
Code: 48 81 64 24 08 00 02 00 00 44 89 fe 6a 00 4c 89 f7 6a 00 ff b4 24 f8 00 00 00 ff 74 24 18 41 0f 94 c1 45 0f b6 c9 e8 b5 94 ff <ff> 48 c7 c7 a0 8a cc 89 48 83 c4 20 e8 25 68 19 08 b8 ff ff ff ff
RSP: 0018:ffffc90013b2f9e8 EFLAGS: 00010092
RAX: 0000000000000001 RBX: 1ffff92002765f43 RCX: ffffffff815e4bee
RDX: 1ffff11003c8b8ae RSI: 0000000000000001 RDI: ffffffff8f67d5d8
RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffff9068e94f
R10: fffffbfff20d1d29 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000000000000 R14: ffff88801dac49d8 R15: 0000000000000000
FS: 00007fc2d48ce700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffc8 CR3: 000000002043b000 CR4: 0000000000350ef0
Call Trace:
<TASK>
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:349 [inline]
inode_sb_list_del fs/inode.c:502 [inline]
evict+0x179/0x6b0 fs/inode.c:653
iput_final fs/inode.c:1744 [inline]
iput.part.0+0x562/0x820 fs/inode.c:1770
iput+0x58/0x70 fs/inode.c:1760
ntfs_fill_super+0x2d75/0x3750 fs/ntfs3/super.c:1180
get_tree_bdev+0x440/0x760 fs/super.c:1292
vfs_get_tree+0x89/0x2f0 fs/super.c:1497
do_new_mount fs/namespace.c:3040 [inline]
path_mount+0x1320/0x1fa0 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc2d368a73a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc2d48cdf88 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007fc2d368a73a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fc2d48cdfe0
RBP: 00007fc2d48ce020 R08: 00007fc2d48ce020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000020000000
R13: 0000000020000100 R14: 00007fc2d48cdfe0 R15: 000000002007aa80
</TASK>
Modules linked in:
CR2: ffffffffffffffc8
---[ end trace 0000000000000000 ]---
RIP: 0010:lock_acquire kernel/locking/lockdep.c:5666 [inline]
RIP: 0010:lock_acquire+0x1aa/0x570 kernel/locking/lockdep.c:5631
Code: 48 81 64 24 08 00 02 00 00 44 89 fe 6a 00 4c 89 f7 6a 00 ff b4 24 f8 00 00 00 ff 74 24 18 41 0f 94 c1 45 0f b6 c9 e8 b5 94 ff <ff> 48 c7 c7 a0 8a cc 89 48 83 c4 20 e8 25 68 19 08 b8 ff ff ff ff
RSP: 0018:ffffc90013b2f9e8 EFLAGS: 00010092
RAX: 0000000000000001 RBX: 1ffff92002765f43 RCX: ffffffff815e4bee
RDX: 1ffff11003c8b8ae RSI: 0000000000000001 RDI: ffffffff8f67d5d8
RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffff9068e94f
R10: fffffbfff20d1d29 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000000000000 R14: ffff88801dac49d8 R15: 0000000000000000
FS: 00007fc2d48ce700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffc8 CR3: 000000002043b000 CR4: 0000000000350ef0
---
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.
next reply other threads:[~2022-09-24 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 23:36 syzbot [this message]
2022-09-25 4:19 ` [syzbot] BUG: unable to handle kernel paging request in evict syzbot
2023-01-24 8:57 ` syzbot
2023-01-27 7:17 ` Dmitry Vyukov
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=000000000000e4630c05e974c1eb@google.com \
--to=syzbot+6b74cf8fcd7378d8be7c@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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.