From: syzbot <syzbot+9af29acd8f27fbce94bc@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] general protection fault in run_is_mapped_full
Date: Mon, 15 Jul 2024 02:39:02 -0700 [thread overview]
Message-ID: <000000000000d92e6a061d45ffa3@google.com> (raw)
In-Reply-To: <8f3f2481-c970-4019-b39d-6f0d280ba147@paragon-software.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
general protection fault in run_is_mapped_full
loop0: detected capacity change from 0 to 4096
ntfs3: loop0: Different NTFS sector size (1024) and media sector size (512).
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
CPU: 1 PID: 6004 Comm: syz.0.15 Not tainted 6.10.0-rc1-syzkaller-00034-geb95678ee930 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:run_lookup fs/ntfs3/run.c:39 [inline]
RIP: 0010:run_is_mapped_full+0x35/0x480 fs/ntfs3/run.c:173
Code: 41 54 53 48 83 ec 30 41 89 d4 41 89 f6 49 89 fd 49 bf 00 00 00 00 00 fc ff df e8 36 e5 a7 fe 49 8d 5d 08 48 89 d8 48 c1 e8 03 <42> 80 3c 38 00 74 08 48 89 df e8 6c 9c 0d ff 48 8b 1b 31 ff 48 89
RSP: 0018:ffffc9000329f758 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 0000000000000008 RCX: ffff88807b0c5a00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000329fb18 R08: ffffffff82e4ba0a R09: ffffffff82ee0999
R10: 0000000000000002 R11: ffff88807b0c5a00 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: dffffc0000000000
FS: 00007f826d7ef6c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb79d6ff095 CR3: 000000007ccc0000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
attr_load_runs fs/ntfs3/attrib.c:69 [inline]
attr_set_size+0xfdf/0x4300 fs/ntfs3/attrib.c:502
ntfs_create_inode+0x252d/0x37f0 fs/ntfs3/inode.c:1719
ntfs_symlink+0xde/0x110 fs/ntfs3/namei.c:199
vfs_symlink+0x137/0x2e0 fs/namei.c:4489
do_symlinkat+0x222/0x3a0 fs/namei.c:4515
__do_sys_symlinkat fs/namei.c:4531 [inline]
__se_sys_symlinkat fs/namei.c:4528 [inline]
__x64_sys_symlinkat+0x99/0xb0 fs/namei.c:4528
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f826c975bd9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f826d7ef048 EFLAGS: 00000246 ORIG_RAX: 000000000000010a
RAX: ffffffffffffffda RBX: 00007f826cb03f60 RCX: 00007f826c975bd9
RDX: 0000000020000440 RSI: 0000000000000006 RDI: 0000000020000340
RBP: 00007f826c9e4e60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f826cb03f60 R15: 00007ffc50a8ce78
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:run_lookup fs/ntfs3/run.c:39 [inline]
RIP: 0010:run_is_mapped_full+0x35/0x480 fs/ntfs3/run.c:173
Code: 41 54 53 48 83 ec 30 41 89 d4 41 89 f6 49 89 fd 49 bf 00 00 00 00 00 fc ff df e8 36 e5 a7 fe 49 8d 5d 08 48 89 d8 48 c1 e8 03 <42> 80 3c 38 00 74 08 48 89 df e8 6c 9c 0d ff 48 8b 1b 31 ff 48 89
RSP: 0018:ffffc9000329f758 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 0000000000000008 RCX: ffff88807b0c5a00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000329fb18 R08: ffffffff82e4ba0a R09: ffffffff82ee0999
R10: 0000000000000002 R11: ffff88807b0c5a00 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: dffffc0000000000
FS: 00007f826d7ef6c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f826cb000a0 CR3: 000000007ccc0000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 41 54 push %r12
2: 53 push %rbx
3: 48 83 ec 30 sub $0x30,%rsp
7: 41 89 d4 mov %edx,%r12d
a: 41 89 f6 mov %esi,%r14d
d: 49 89 fd mov %rdi,%r13
10: 49 bf 00 00 00 00 00 movabs $0xdffffc0000000000,%r15
17: fc ff df
1a: e8 36 e5 a7 fe call 0xfea7e555
1f: 49 8d 5d 08 lea 0x8(%r13),%rbx
23: 48 89 d8 mov %rbx,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 48 89 df mov %rbx,%rdi
34: e8 6c 9c 0d ff call 0xff0d9ca5
39: 48 8b 1b mov (%rbx),%rbx
3c: 31 ff xor %edi,%edi
3e: 48 rex.W
3f: 89 .byte 0x89
Tested on:
commit: eb95678e fs/ntfs3: Keep runs for $MFT::$ATTR_DATA and ..
git tree: https://github.com/Paragon-Software-Group/linux-ntfs3.git
console output: https://syzkaller.appspot.com/x/log.txt?x=16543f85980000
kernel config: https://syzkaller.appspot.com/x/.config?x=2f1c94a15f7c9744
dashboard link: https://syzkaller.appspot.com/bug?extid=9af29acd8f27fbce94bc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
next parent reply other threads:[~2024-07-15 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8f3f2481-c970-4019-b39d-6f0d280ba147@paragon-software.com>
2024-07-15 9:39 ` syzbot [this message]
[not found] <20240902130045.6945-1-almaz.alexandrovich@paragon-software.com>
2024-09-12 13:19 ` [syzbot] [ntfs3?] general protection fault in run_is_mapped_full syzbot
[not found] <706373e55157441da446a4d634784706@paragon-software.com>
2024-08-27 17:23 ` syzbot
[not found] <be1ba54b-80a1-4cf2-9a2d-395e87c53a28@paragon-software.com>
2024-07-15 10:01 ` syzbot
[not found] <6da7776f-51a3-4d3c-83e9-e3b710eef541@paragon-software.com>
2024-07-15 9:23 ` syzbot
2024-07-13 6:10 syzbot
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=000000000000d92e6a061d45ffa3@google.com \
--to=syzbot+9af29acd8f27fbce94bc@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.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.