All of lore.kernel.org
 help / color / mirror / Atom feed
* [syzbot] UBSAN: array-index-out-of-bounds in xtSearch
@ 2022-10-04  8:50 syzbot
  2022-12-25  4:15 ` [syzbot] [jfs?] " syzbot
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: syzbot @ 2022-10-04  8:50 UTC (permalink / raw)
  To: jfs-discussion, linux-kernel, shaggy, syzkaller-bugs

Hello,

syzbot found the following issue on:

HEAD commit:    a962b54e162c Merge tag 'i2c-for-6.0-rc8' of git://git.kern..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1441fa0a880000
kernel config:  https://syzkaller.appspot.com/x/.config?x=ba0d23aa7e1ffaf5
dashboard link: https://syzkaller.appspot.com/bug?extid=76a072c2f8a60280bd70
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7cf7771c181a/disk-a962b54e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dcd5516984d8/vmlinux-a962b54e.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+76a072c2f8a60280bd70@syzkaller.appspotmail.com

================================================================================
UBSAN: array-index-out-of-bounds in fs/jfs/jfs_xtree.c:360:4
index 19 is out of range for type 'xad_t [18]'
CPU: 1 PID: 1533 Comm: syz-executor.1 Not tainted 6.0.0-rc7-syzkaller-00250-ga962b54e162c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106
 ubsan_epilogue lib/ubsan.c:151 [inline]
 __ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283
 xtSearch+0x709/0x1cb0 fs/jfs/jfs_xtree.c:360
 xtLookup+0x235/0x880 fs/jfs/jfs_xtree.c:152
 extHint+0x204/0x630 fs/jfs/jfs_extent.c:215
 jfs_get_block+0x2e3/0xce0 fs/jfs/inode.c:246
 __block_write_begin_int+0x5f6/0x1ba0 fs/buffer.c:2006
 __block_write_begin fs/buffer.c:2056 [inline]
 block_write_begin+0x93/0x1e0 fs/buffer.c:2117
 jfs_write_begin+0x2d/0x60 fs/jfs/inode.c:304
 generic_perform_write+0x2a8/0x5b0 mm/filemap.c:3738
 __generic_file_write_iter+0x176/0x400 mm/filemap.c:3866
 generic_file_write_iter+0xab/0x310 mm/filemap.c:3898
 do_iter_write+0x6c2/0xc20 fs/read_write.c:861
 iter_file_splice_write+0x7fc/0xfc0 fs/splice.c:686
 do_splice_from fs/splice.c:764 [inline]
 direct_splice_actor+0xe6/0x1c0 fs/splice.c:931
 splice_direct_to_actor+0x4e4/0xc00 fs/splice.c:886
 do_splice_direct+0x279/0x3d0 fs/splice.c:974
 do_sendfile+0x5fb/0xf80 fs/read_write.c:1255
 __do_sys_sendfile64 fs/read_write.c:1323 [inline]
 __se_sys_sendfile64+0x14f/0x1b0 fs/read_write.c:1309
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7efc6de8a5a9
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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007efc6cddd168 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007efc6dfac050 RCX: 00007efc6de8a5a9
RDX: 0000000000000000 RSI: 0000000000000007 RDI: 0000000000000003
RBP: 00007efc6dee5580 R08: 0000000000000000 R09: 0000000000000000
R10: 00008400fffffffa R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe1677525f R14: 00007efc6cddd300 R15: 0000000000022000
 </TASK>
================================================================================


---
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.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in xtSearch
  2022-10-04  8:50 [syzbot] UBSAN: array-index-out-of-bounds in xtSearch syzbot
@ 2022-12-25  4:15 ` syzbot
  2023-07-16  0:39 ` syzbot
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: syzbot @ 2022-12-25  4:15 UTC (permalink / raw)
  To: jfs-discussion, linux-kernel, shaggy, syzkaller-bugs

syzbot has found a reproducer for the following issue on:

HEAD commit:    72a85e2b0a1e Merge tag 'spi-fix-v6.2-rc1' of git://git.ker..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16d22974480000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4e2d7bfa2d6d5a76
dashboard link: https://syzkaller.appspot.com/bug?extid=76a072c2f8a60280bd70
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15802088480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/510d16df06c8/disk-72a85e2b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/50ef5477a1d4/vmlinux-72a85e2b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f2acd6f1189a/bzImage-72a85e2b.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/5e378294b8d6/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+76a072c2f8a60280bd70@syzkaller.appspotmail.com

================================================================================
UBSAN: array-index-out-of-bounds in fs/jfs/jfs_xtree.c:360:4
index 19 is out of range for type 'xad_t [18]'
CPU: 1 PID: 5414 Comm: syz-executor.0 Not tainted 6.1.0-syzkaller-14594-g72a85e2b0a1e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1b1/0x290 lib/dump_stack.c:106
 ubsan_epilogue lib/ubsan.c:151 [inline]
 __ubsan_handle_out_of_bounds+0xe0/0x110 lib/ubsan.c:282
 xtSearch+0x709/0x1cb0 fs/jfs/jfs_xtree.c:360
 xtLookup+0x235/0x880 fs/jfs/jfs_xtree.c:152
 extHint+0x204/0x630 fs/jfs/jfs_extent.c:215
 jfs_get_block+0x2e3/0xce0 fs/jfs/inode.c:246
 get_more_blocks fs/direct-io.c:665 [inline]
 do_direct_IO fs/direct-io.c:953 [inline]
 __blockdev_direct_IO+0x1737/0x3bf0 fs/direct-io.c:1266
 blockdev_direct_IO include/linux/fs.h:3213 [inline]
 jfs_direct_IO+0xf6/0x1e0 fs/jfs/inode.c:331
 generic_file_direct_write+0x294/0x610 mm/filemap.c:3696
 __generic_file_write_iter+0x1c4/0x400 mm/filemap.c:3856
 generic_file_write_iter+0xab/0x310 mm/filemap.c:3932
 do_iter_write+0x6c2/0xc20 fs/read_write.c:861
 iter_file_splice_write+0x7fc/0xfc0 fs/splice.c:686
 do_splice_from fs/splice.c:764 [inline]
 direct_splice_actor+0xe6/0x1c0 fs/splice.c:931
 splice_direct_to_actor+0x4e4/0xc00 fs/splice.c:886
 do_splice_direct+0x279/0x3d0 fs/splice.c:974
 do_sendfile+0x5fb/0xf80 fs/read_write.c:1255
 __do_sys_sendfile64 fs/read_write.c:1323 [inline]
 __se_sys_sendfile64+0x14f/0x1b0 fs/read_write.c:1309
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f9065c8c0a9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f90669ab168 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f9065dac050 RCX: 00007f9065c8c0a9
RDX: 0000000000000000 RSI: 0000000000000008 RDI: 0000000000000007
RBP: 00007f9065ce7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 000080001d00c0d0 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe07df477f R14: 00007f90669ab300 R15: 0000000000022000
 </TASK>
================================================================================


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in xtSearch
  2022-10-04  8:50 [syzbot] UBSAN: array-index-out-of-bounds in xtSearch syzbot
  2022-12-25  4:15 ` [syzbot] [jfs?] " syzbot
@ 2023-07-16  0:39 ` syzbot
  2023-11-25 23:21 ` syzbot
  2023-11-28 19:47 ` [syzbot] " syzbot
  3 siblings, 0 replies; 5+ messages in thread
From: syzbot @ 2023-07-16  0:39 UTC (permalink / raw)
  To: jfs-discussion, linux-fsdevel, linux-kernel, shaggy, syzkaller-bugs

syzbot has found a reproducer for the following issue on:

HEAD commit:    b6e6cc1f78c7 Merge tag 'x86_urgent_for_6.5_rc2' of git://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11f40fa2a80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4a9506b1ca57ae9f
dashboard link: https://syzkaller.appspot.com/bug?extid=76a072c2f8a60280bd70
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=172c5646a80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13360a92a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3dfa34d80a41/disk-b6e6cc1f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/778e016c7229/vmlinux-b6e6cc1f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c8001018a584/bzImage-b6e6cc1f.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/36bab007b655/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+76a072c2f8a60280bd70@syzkaller.appspotmail.com

================================================================================
UBSAN: array-index-out-of-bounds in fs/jfs/jfs_xtree.c:360:4
index 18 is out of range for type 'xad_t [18]'
CPU: 0 PID: 5017 Comm: syz-executor116 Not tainted 6.5.0-rc1-syzkaller-00248-gb6e6cc1f78c7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x125/0x1b0 lib/dump_stack.c:106
 ubsan_epilogue lib/ubsan.c:217 [inline]
 __ubsan_handle_out_of_bounds+0x111/0x150 lib/ubsan.c:348
 xtSearch+0x12e2/0x1650 fs/jfs/jfs_xtree.c:360
 xtLookup+0x273/0x840 fs/jfs/jfs_xtree.c:152
 jfs_get_block+0x325/0xb20 fs/jfs/inode.c:218
 do_mpage_readpage+0x6f8/0x1ab0 fs/mpage.c:234
 mpage_readahead+0x344/0x580 fs/mpage.c:382
 read_pages+0x1d1/0xda0 mm/readahead.c:160
 page_cache_ra_unbounded+0x457/0x5e0 mm/readahead.c:269
 do_page_cache_ra mm/readahead.c:299 [inline]
 page_cache_ra_order+0x72b/0xa80 mm/readahead.c:559
 ondemand_readahead+0x540/0x1150 mm/readahead.c:681
 page_cache_sync_ra+0x174/0x1d0 mm/readahead.c:708
 page_cache_sync_readahead include/linux/pagemap.h:1213 [inline]
 filemap_get_pages+0xc05/0x1820 mm/filemap.c:2563
 filemap_splice_read+0x3d0/0x9f0 mm/filemap.c:2925
 vfs_splice_read fs/splice.c:994 [inline]
 vfs_splice_read+0x2c8/0x3b0 fs/splice.c:963
 splice_direct_to_actor+0x2a5/0xa30 fs/splice.c:1070
 do_splice_direct+0x1af/0x280 fs/splice.c:1195
 do_sendfile+0xb88/0x1390 fs/read_write.c:1254
 __do_sys_sendfile64 fs/read_write.c:1322 [inline]
 __se_sys_sendfile64 fs/read_write.c:1308 [inline]
 __x64_sys_sendfile64+0x1d6/0x220 fs/read_write.c:1308
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f9707d0abc9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 81 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:00007f97008a5168 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f9707d97718 RCX: 00007f9707d0abc9
RDX: 0000000000000000 RSI: 0000000000000007 RDI: 0000000000000006
RBP: 00007f9707d97710 R08: 00007f97008a56c0 R09: 0000000000000000
R10: 0001000000201004 R11: 0000000000000246 R12: 00007f9707d9771c
R13: 000000000000006e R14: 00007ffe2c345d70 R15: 00007ffe2c345e58
 </TASK>
================================================================================


---
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.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in xtSearch
  2022-10-04  8:50 [syzbot] UBSAN: array-index-out-of-bounds in xtSearch syzbot
  2022-12-25  4:15 ` [syzbot] [jfs?] " syzbot
  2023-07-16  0:39 ` syzbot
@ 2023-11-25 23:21 ` syzbot
  2023-11-28 19:47 ` [syzbot] " syzbot
  3 siblings, 0 replies; 5+ messages in thread
From: syzbot @ 2023-11-25 23:21 UTC (permalink / raw)
  To: cuigaosheng1, dave.kleikamp, ghandatmanas, jfs-discussion,
	juntong.deng, linux-fsdevel, linux-kernel-mentees, linux-kernel,
	shaggy, syzkaller-bugs, syzkaller

syzbot suspects this issue was fixed by commit:

commit a779ed754e52d582b8c0e17959df063108bd0656
Author: Dave Kleikamp <dave.kleikamp@oracle.com>
Date:   Thu Oct 5 14:16:14 2023 +0000

    jfs: define xtree root and page independently

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=16eb55af680000
start commit:   72a85e2b0a1e Merge tag 'spi-fix-v6.2-rc1' of git://git.ker..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=4e2d7bfa2d6d5a76
dashboard link: https://syzkaller.appspot.com/bug?extid=76a072c2f8a60280bd70
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15802088480000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: jfs: define xtree root and page independently

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [syzbot] Re: [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in xtSearch
  2022-10-04  8:50 [syzbot] UBSAN: array-index-out-of-bounds in xtSearch syzbot
                   ` (2 preceding siblings ...)
  2023-11-25 23:21 ` syzbot
@ 2023-11-28 19:47 ` syzbot
  3 siblings, 0 replies; 5+ messages in thread
From: syzbot @ 2023-11-28 19:47 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in xtSearch
Author: dave.kleikamp@oracle.com

#syz fix: jfs: define xtree root and page independently

On 11/25/23 5:21PM, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
> 
> commit a779ed754e52d582b8c0e17959df063108bd0656
> Author: Dave Kleikamp <dave.kleikamp@oracle.com>
> Date:   Thu Oct 5 14:16:14 2023 +0000
> 
>      jfs: define xtree root and page independently
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=16eb55af680000
> start commit:   72a85e2b0a1e Merge tag 'spi-fix-v6.2-rc1' of git://git.ker..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=4e2d7bfa2d6d5a76
> dashboard link: https://syzkaller.appspot.com/bug?extid=76a072c2f8a60280bd70
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15802088480000
> 
> If the result looks correct, please mark the issue as fixed by replying with:
> 
> #syz fix: jfs: define xtree root and page independently
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2023-11-28 19:48 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-04  8:50 [syzbot] UBSAN: array-index-out-of-bounds in xtSearch syzbot
2022-12-25  4:15 ` [syzbot] [jfs?] " syzbot
2023-07-16  0:39 ` syzbot
2023-11-25 23:21 ` syzbot
2023-11-28 19:47 ` [syzbot] " syzbot

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.