From: syzbot <syzbot+e381e4c52ca8a53c3af7@syzkaller.appspotmail.com>
To: jack@suse.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [udf?] WARNING in __udf_add_aext (2)
Date: Fri, 30 Jun 2023 04:12:46 -0700 [thread overview]
Message-ID: <00000000000089621005ff56e57c@google.com> (raw)
In-Reply-To: <00000000000049c61505fe026632@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: b19edac5992d Merge tag 'nolibc.2023.06.22a' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1425350b280000
kernel config: https://syzkaller.appspot.com/x/.config?x=33c8c2baba1cfc7e
dashboard link: https://syzkaller.appspot.com/bug?extid=e381e4c52ca8a53c3af7
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1515b4f0a80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e1a4f239105a/disk-b19edac5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/25776c3e9785/vmlinux-b19edac5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ca7e959d451d/bzImage-b19edac5.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/531715d2031b/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e381e4c52ca8a53c3af7@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5874 at fs/udf/inode.c:2050 __udf_add_aext+0x550/0x6f0
Modules linked in:
CPU: 1 PID: 5874 Comm: syz-executor.0 Not tainted 6.4.0-syzkaller-01312-gb19edac5992d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:__udf_add_aext+0x550/0x6f0 fs/udf/inode.c:2049
Code: 4c 89 e7 e8 02 1d e3 fe 49 8b 3c 24 4c 89 fe e8 56 21 03 ff 31 c0 48 83 c4 30 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 e0 26 8b fe <0f> 0b e9 ed fb ff ff e8 d4 26 8b fe 0f 0b e9 5c fc ff ff e8 c8 26
RSP: 0018:ffffc900069a6af8 EFLAGS: 00010293
RAX: ffffffff83008300 RBX: 1ffff92000d34df9 RCX: ffff888028cb8000
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff83007ee6 R09: ffffffff83007e16
R10: 0000000000000002 R11: ffff888028cb8000 R12: ffffc900069a6fc0
R13: 0000000000000004 R14: dffffc0000000000 R15: ffffc900069a6fc8
FS: 00007f9f9186d700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9f9182c000 CR3: 000000001f981000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
udf_add_aext fs/udf/inode.c:2107 [inline]
udf_do_extend_file+0xcb5/0x11e0 fs/udf/inode.c:592
inode_getblk fs/udf/inode.c:822 [inline]
udf_map_block+0x16c0/0x4ff0 fs/udf/inode.c:450
__udf_get_block+0x126/0x410 fs/udf/inode.c:464
__block_write_begin_int+0x548/0x1a50 fs/buffer.c:2063
__block_write_begin fs/buffer.c:2113 [inline]
block_write_begin+0x9c/0x1f0 fs/buffer.c:2174
udf_write_begin+0x10d/0x1a0 fs/udf/inode.c:265
generic_perform_write+0x300/0x5e0 mm/filemap.c:3946
__generic_file_write_iter+0x17a/0x400 mm/filemap.c:4074
udf_file_write_iter+0x2fd/0x660 fs/udf/file.c:115
do_iter_write+0x84f/0xde0 fs/read_write.c:860
iter_file_splice_write+0x843/0xfe0 fs/splice.c:762
do_splice_from fs/splice.c:840 [inline]
direct_splice_actor+0xea/0x1c0 fs/splice.c:1027
splice_direct_to_actor+0x37e/0x9a0 fs/splice.c:982
do_splice_direct+0x286/0x3d0 fs/splice.c:1070
do_sendfile+0x623/0x1070 fs/read_write.c:1254
__do_sys_sendfile64 fs/read_write.c:1322 [inline]
__se_sys_sendfile64+0x17c/0x1e0 fs/read_write.c:1308
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f9f90a8c389
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:00007f9f9186d168 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f9f90babf80 RCX: 00007f9f90a8c389
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000005
RBP: 00007f9f90ad7493 R08: 0000000000000000 R09: 0000000000000000
R10: 0001000000201005 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe5898ad1f R14: 00007f9f9186d300 R15: 0000000000022000
</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.
next prev parent reply other threads:[~2023-06-30 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 12:59 [syzbot] [udf?] WARNING in __udf_add_aext (2) syzbot
2023-06-30 11:12 ` syzbot [this message]
2024-01-10 14:56 ` syzbot
2024-01-16 12:29 ` Jan Kara
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=00000000000089621005ff56e57c@google.com \
--to=syzbot+e381e4c52ca8a53c3af7@syzkaller.appspotmail.com \
--cc=jack@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).