lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <6716f9e2.050a0220.1e4b4d.0068.GAE@google.com>
Date: Mon, 21 Oct 2024 18:03:30 -0700
From: syzbot <syzbot+9295d5153c44d86af0aa@...kaller.appspotmail.com>
To: clm@...com, dsterba@...e.com, josef@...icpanda.com, 
	linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com
Subject: [syzbot] [btrfs?] kernel BUG in extent_writepage_io

Hello,

syzbot found the following issue on:

HEAD commit:    6efbea77b390 Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11c0c240580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=164d2822debd8b0d
dashboard link: https://syzkaller.appspot.com/bug?extid=9295d5153c44d86af0aa
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15c18c5f980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12186f27980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5dbbf0b1a9a5/disk-6efbea77.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fd272a84cc09/vmlinux-6efbea77.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cfcfcf079289/bzImage-6efbea77.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/504c13bf000c/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9295d5153c44d86af0aa@...kaller.appspotmail.com

assertion failed: block_start != EXTENT_MAP_HOLE, in fs/btrfs/extent_io.c:1303
------------[ cut here ]------------
kernel BUG at fs/btrfs/extent_io.c:1303!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 0 UID: 0 PID: 5258 Comm: syz-executor179 Not tainted 6.12.0-rc3-syzkaller-00183-g6efbea77b390 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:submit_one_sector fs/btrfs/extent_io.c:1303 [inline]
RIP: 0010:extent_writepage_io+0xca2/0xd20 fs/btrfs/extent_io.c:1388
Code: fe 07 90 0f 0b e8 1e 28 d9 fd 48 c7 c7 80 0d 4d 8c 48 c7 c6 60 1b 4d 8c 48 c7 c2 20 0d 4d 8c b9 17 05 00 00 e8 5f f7 fe 07 90 <0f> 0b e8 f7 27 d9 fd eb 5f e8 f0 27 d9 fd 48 c7 c7 80 0d 4d 8c 48
RSP: 0018:ffffc90003eb6ec0 EFLAGS: 00010246
RAX: 000000000000004e RBX: 0000000000001000 RCX: 9c772e8b3e6d6f00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90003eb7030 R08: ffffffff8174af9c R09: 1ffff920007d6d74
R10: dffffc0000000000 R11: fffff520007d6d75 R12: fffffffffffffffd
R13: 0000000000007000 R14: dffffc0000000000 R15: ffffea0001c3a740
FS:  00007f6de66216c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020948000 CR3: 0000000076e7c000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 extent_writepage fs/btrfs/extent_io.c:1460 [inline]
 extent_write_cache_pages fs/btrfs/extent_io.c:2130 [inline]
 btrfs_writepages+0x11c4/0x2370 fs/btrfs/extent_io.c:2261
 do_writepages+0x35d/0x870 mm/page-writeback.c:2683
 filemap_fdatawrite_wbc+0x125/0x180 mm/filemap.c:398
 __filemap_fdatawrite_range mm/filemap.c:431 [inline]
 filemap_fdatawrite_range+0x11a/0x180 mm/filemap.c:449
 btrfs_fdatawrite_range+0x53/0xe0 fs/btrfs/file.c:3827
 btrfs_direct_write+0x565/0xa70 fs/btrfs/direct-io.c:961
 btrfs_do_write_iter+0x2a0/0x760 fs/btrfs/file.c:1505
 do_iter_readv_writev+0x600/0x880
 vfs_writev+0x376/0xba0 fs/read_write.c:1064
 do_pwritev fs/read_write.c:1165 [inline]
 __do_sys_pwritev2 fs/read_write.c:1224 [inline]
 __se_sys_pwritev2+0x1ca/0x2d0 fs/read_write.c:1215
 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:0x7f6de66ad5d9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 18 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f6de6621158 EFLAGS: 00000212 ORIG_RAX: 0000000000000148
RAX: ffffffffffffffda RBX: 00007f6de673a6e8 RCX: 00007f6de66ad5d9
RDX: 0000000000000001 RSI: 0000000020000240 RDI: 0000000000000004
RBP: 00007f6de673a6e0 R08: 0000000000000000 R09: 0000000000000003
R10: 0000000000007800 R11: 0000000000000212 R12: 00007f6de673a6ec
R13: 000000000000006e R14: 00007fffacb4cff0 R15: 00007fffacb4d0d8
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:submit_one_sector fs/btrfs/extent_io.c:1303 [inline]
RIP: 0010:extent_writepage_io+0xca2/0xd20 fs/btrfs/extent_io.c:1388
Code: fe 07 90 0f 0b e8 1e 28 d9 fd 48 c7 c7 80 0d 4d 8c 48 c7 c6 60 1b 4d 8c 48 c7 c2 20 0d 4d 8c b9 17 05 00 00 e8 5f f7 fe 07 90 <0f> 0b e8 f7 27 d9 fd eb 5f e8 f0 27 d9 fd 48 c7 c7 80 0d 4d 8c 48
RSP: 0018:ffffc90003eb6ec0 EFLAGS: 00010246
RAX: 000000000000004e RBX: 0000000000001000 RCX: 9c772e8b3e6d6f00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90003eb7030 R08: ffffffff8174af9c R09: 1ffff920007d6d74
R10: dffffc0000000000 R11: fffff520007d6d75 R12: fffffffffffffffd
R13: 0000000000007000 R14: dffffc0000000000 R15: ffffea0001c3a740
FS:  00007f6de66216c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005646f9cff0b8 CR3: 0000000076e7c000 CR4: 00000000003526f0
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@...glegroups.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 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 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ