From: syzbot <syzbot+43fc5ba6dcb33e3261ca@syzkaller.appspotmail.com>
To: axboe@kernel.dk, bvanassche@acm.org, chaitanya.kulkarni@wdc.com,
jack@suse.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in udf_truncate_extents
Date: Mon, 10 Oct 2022 09:07:37 -0700 [thread overview]
Message-ID: <000000000000b94e9e05eab05b00@google.com> (raw)
In-Reply-To: <000000000000b9fad405b179289b@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 4899a36f91a9 Merge tag 'powerpc-6.1-1' of git://git.kernel..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=10260ea4880000
kernel config: https://syzkaller.appspot.com/x/.config?x=e2021a61197ebe02
dashboard link: https://syzkaller.appspot.com/bug?extid=43fc5ba6dcb33e3261ca
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=154bdf0a880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1548ca78880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1a98722ff83f/disk-4899a36f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7a31d6690395/vmlinux-4899a36f.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/a6d9d98c8bd8/mount_0.gz
The issue was bisected to:
commit 2004bfdef945fe55196db6b9cdf321fbc75bb0de
Author: Bart Van Assche <bvanassche@acm.org>
Date: Tue Mar 10 04:26:21 2020 +0000
null_blk: Fix the null_add_dev() error path
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10110920500000
final oops: https://syzkaller.appspot.com/x/report.txt?x=12110920500000
console output: https://syzkaller.appspot.com/x/log.txt?x=14110920500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+43fc5ba6dcb33e3261ca@syzkaller.appspotmail.com
Fixes: 2004bfdef945 ("null_blk: Fix the null_add_dev() error path")
loop0: detected capacity change from 0 to 2048
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3622 at fs/udf/truncate.c:226 udf_truncate_extents+0x844/0x930 fs/udf/truncate.c:226
Modules linked in:
CPU: 1 PID: 3622 Comm: syz-executor198 Not tainted 6.0.0-syzkaller-09413-g4899a36f91a9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
RIP: 0010:udf_truncate_extents+0x844/0x930 fs/udf/truncate.c:226
Code: 84 d2 74 05 e8 bd db f2 fe 8b 44 24 20 be 07 00 00 00 48 89 df 89 83 cc fe ff ff e8 56 ec 0d ff e9 a5 fd ff ff e8 0c c5 a5 fe <0f> 0b e9 1f fe ff ff e8 00 c5 a5 fe 0f 0b 48 8b 7c 24 18 e8 24 db
RSP: 0018:ffffc900040ef9d8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88806fc3d4a0 RCX: 0000000000000000
RDX: ffff88801dc10000 RSI: ffffffff82d58224 RDI: 0000000000000007
RBP: ffffc900040efac0 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000200 R11: 000000000008c07c R12: ffffc900040efa80
R13: 0000000000000200 R14: 00000000000000ff R15: ffff88807e738000
FS: 000055555697f300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002000e000 CR3: 000000001bebe000 CR4: 0000000000350ee0
Call Trace:
<TASK>
udf_write_failed.isra.0+0x173/0x1c0 fs/udf/inode.c:179
udf_write_begin+0x7f/0xa0 fs/udf/inode.c:214
generic_perform_write+0x246/0x560 mm/filemap.c:3745
__generic_file_write_iter+0x2aa/0x4d0 mm/filemap.c:3873
udf_file_write_iter+0x2cc/0x650 fs/udf/file.c:170
call_write_iter include/linux/fs.h:2190 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x9e9/0xdd0 fs/read_write.c:584
ksys_write+0x127/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f305ad3c8f9
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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff2d740688 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000200001c0 RCX: 00007f305ad3c8f9
RDX: 000000000208e24b RSI: 0000000020000040 RDI: 0000000000000003
RBP: 0000000000000000 R08: 00007fff2d7406b0 R09: 00007fff2d7406b0
R10: 00007fff2d740560 R11: 0000000000000246 R12: 00007fff2d7406ac
R13: 00007fff2d7406e0 R14: 00007fff2d7406c0 R15: 0000000000000009
</TASK>
prev parent reply other threads:[~2022-10-10 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 13:20 WARNING in udf_truncate_extents syzbot
2020-10-13 4:17 ` Bart Van Assche
2020-10-13 4:17 ` syzbot
2020-10-13 4:17 ` syzbot
2022-10-10 16:07 ` syzbot [this message]
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=000000000000b94e9e05eab05b00@google.com \
--to=syzbot+43fc5ba6dcb33e3261ca@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=chaitanya.kulkarni@wdc.com \
--cc=jack@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox