From: syzbot <syzbot+f5b965c58efb9c510227@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, brauner@kernel.org,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu, viro@zeniv.linux.org.uk
Subject: [syzbot] [ext4?] general protection fault in inode_permission (2)
Date: Thu, 31 Aug 2023 08:12:00 -0700 [thread overview]
Message-ID: <0000000000003ffd3806043977e1@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 28f20a19294d Merge tag 'x86-urgent-2023-08-26' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=153271dfa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=1e4a882f77ed77bd
dashboard link: https://syzkaller.appspot.com/bug?extid=f5b965c58efb9c510227
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16aab870680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=175a687ba80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6b7215a1c9ca/disk-28f20a19.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c5935df3c66a/vmlinux-28f20a19.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3974ee7fd77d/bzImage-28f20a19.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/4d843a4575f5/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f5b965c58efb9c510227@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xeeb017db1ffff112: 0000 [#1] PREEMPT SMP KASAN
KASAN: maybe wild-memory-access in range [0x7580ded8ffff8890-0x7580ded8ffff8897]
CPU: 0 PID: 5055 Comm: syz-executor397 Not tainted 6.5.0-rc7-syzkaller-00185-g28f20a19294d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
RIP: 0010:do_inode_permission fs/namei.c:460 [inline]
RIP: 0010:inode_permission fs/namei.c:528 [inline]
RIP: 0010:inode_permission+0x35d/0x5e0 fs/namei.c:503
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 5d 02 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 73 20 49 8d 7e 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 30 02 00 00 4d 8b 76 10 4d 85 f6 0f 84 ab 01 00
RSP: 0000:ffffc90003caf5a0 EFLAGS: 00010216
RAX: dffffc0000000000 RBX: ffff88807580dcb0 RCX: 0000000000000000
RDX: 0eb01bdb1ffff112 RSI: ffffffff81ec15b5 RDI: 7580ded8ffff8890
RBP: 0000000000000081 R08: 0000000000000003 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffffffff8cb84420
R13: 0000000000000000 R14: 7580ded8ffff8880 R15: ffff88807580dcb2
FS: 0000555555f8d3c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffc7 CR3: 000000002a981000 CR4: 0000000000350ef0
Call Trace:
<TASK>
may_lookup fs/namei.c:1716 [inline]
link_path_walk.part.0.constprop.0+0x26f/0xce0 fs/namei.c:2267
link_path_walk fs/namei.c:2250 [inline]
path_parentat+0xaa/0x1b0 fs/namei.c:2526
__filename_parentat+0x1f2/0x640 fs/namei.c:2550
filename_parentat fs/namei.c:2568 [inline]
do_unlinkat+0x109/0x6d0 fs/namei.c:4368
do_coredump+0x18bd/0x3fc0 fs/coredump.c:675
get_signal+0x2464/0x2770 kernel/signal.c:2867
arch_do_signal_or_restart+0x89/0x5f0 arch/x86/kernel/signal.c:308
exit_to_user_mode_loop kernel/entry/common.c:168 [inline]
exit_to_user_mode_prepare+0x11f/0x240 kernel/entry/common.c:204
irqentry_exit_to_user_mode+0x9/0x40 kernel/entry/common.c:310
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7f96f653c143
Code: e8 46 45 00 00 66 0f 1f 44 00 00 48 83 ec 08 48 89 fa 48 89 f1 31 ff 31 f6 e8 4d 01 03 00 85 c0 75 09 48 83 c4 08 c3 0f 1f 40 <00> 48 c7 c2 b0 ff ff ff 64 89 02 b8 ff ff ff ff eb e6 66 2e 0f 1f
RSP: 002b:00007ffc5e7c7220 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 000000000006cd02 RCX: 00007f96f656c2b3
RDX: 00007ffc5e7c7230 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000066 R08: 00000000000001be R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffc5e7c7300
R13: 0000000000000025 R14: 431bde82d7b634db R15: 00007ffc5e7c7284
</TASK>
Modules linked in:
----------------
Code disassembly (best guess):
0: 48 89 fa mov %rdi,%rdx
3: 48 c1 ea 03 shr $0x3,%rdx
7: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1)
b: 0f 85 5d 02 00 00 jne 0x26e
11: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
18: fc ff df
1b: 4c 8b 73 20 mov 0x20(%rbx),%r14
1f: 49 8d 7e 10 lea 0x10(%r14),%rdi
23: 48 89 fa mov %rdi,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 30 02 00 00 jne 0x264
34: 4d 8b 76 10 mov 0x10(%r14),%r14
38: 4d 85 f6 test %r14,%r14
3b: 0f .byte 0xf
3c: 84 .byte 0x84
3d: ab stos %eax,%es:(%rdi)
3e: 01 00 add %eax,(%rax)
---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
reply other threads:[~2023-08-31 15:12 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=0000000000003ffd3806043977e1@google.com \
--to=syzbot+f5b965c58efb9c510227@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=brauner@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--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.