From: syzbot <syzbot+4a08ffdf3667b36650a1@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, djwong@kernel.org, hch@infradead.org,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
nogikh@google.com, song@kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu,
yukuai3@huawei.com, zhang_shurong@foxmail.com
Subject: Re: [syzbot] [block] kernel BUG in __block_write_begin_int
Date: Tue, 05 Sep 2023 03:04:32 -0700 [thread overview]
Message-ID: <000000000000d9daf4060499c0c9@google.com> (raw)
In-Reply-To: <CANp29Y65sCETzq3CttPHww40W_tQ2S=0HockV-aSUi9dE8HGow@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in __kthread_create_on_node
------------[ cut here ]------------
different return values (11 and 6) from vsnprintf("kmmpd-%.*s", ...)
WARNING: CPU: 1 PID: 12350 at lib/kasprintf.c:31 kvasprintf+0x17b/0x190 lib/kasprintf.c:30
Modules linked in:
CPU: 1 PID: 12350 Comm: syz-executor.0 Not tainted 6.5.0-syzkaller-11705-gfd19eb3c02e0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
RIP: 0010:kvasprintf+0x17b/0x190 lib/kasprintf.c:30
Code: 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 cb db 55 fd 48 c7 c7 a0 0a 59 8b 44 89 e6 89 da 48 8b 4c 24 18 e8 65 56 1c fd <0f> 0b eb 98 e8 2c 46 90 06 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3
RSP: 0018:ffffc90003507620 EFLAGS: 00010246
RAX: 2ce359f82b370100 RBX: 0000000000000006 RCX: ffff88806a543b80
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc900035076f0 R08: ffffffff81541672 R09: 1ffff1101732516a
R10: dffffc0000000000 R11: ffffed101732516b R12: 000000000000000b
R13: ffffc90003507880 R14: 1ffff920006a0ec8 R15: ffff888025476fa0
FS: 00007f224ed5d6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2c420000 CR3: 00000000691b6000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__kthread_create_on_node+0x1a9/0x3c0 kernel/kthread.c:444
kthread_create_on_node+0xde/0x120 kernel/kthread.c:512
ext4_multi_mount_protect+0x792/0x9f0 fs/ext4/mmp.c:392
__ext4_fill_super fs/ext4/super.c:5363 [inline]
ext4_fill_super+0x4495/0x6d10 fs/ext4/super.c:5703
get_tree_bdev+0x416/0x5b0 fs/super.c:1577
vfs_get_tree+0x8c/0x280 fs/super.c:1750
do_new_mount+0x28f/0xae0 fs/namespace.c:3335
do_mount fs/namespace.c:3675 [inline]
__do_sys_mount fs/namespace.c:3884 [inline]
__se_sys_mount+0x2d9/0x3c0 fs/namespace.c:3861
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:0x7f224e07e1ea
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007f224ed5cee8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f224ed5cf80 RCX: 00007f224e07e1ea
RDX: 0000000020000040 RSI: 0000000020000500 RDI: 00007f224ed5cf40
RBP: 0000000020000040 R08: 00007f224ed5cf80 R09: 0000000000004500
R10: 0000000000004500 R11: 0000000000000246 R12: 0000000020000500
R13: 00007f224ed5cf40 R14: 00000000000004b4 R15: 0000000020000540
</TASK>
Tested on:
commit: fd19eb3c iomap: handle error conditions more gracefull..
git tree: git://git.infradead.org/users/hch/misc.git bdev-iomap-fix
console output: https://syzkaller.appspot.com/x/log.txt?x=11955af0680000
kernel config: https://syzkaller.appspot.com/x/.config?x=ff0db7a15ba54ead
dashboard link: https://syzkaller.appspot.com/bug?extid=4a08ffdf3667b36650a1
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
next prev parent reply other threads:[~2023-09-05 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 7:29 [syzbot] [xfs?] [ext4?] kernel BUG in __block_write_begin_int syzbot
2023-09-04 8:11 ` Yu Kuai
2023-09-04 8:33 ` Dave Chinner
2023-09-04 13:26 ` Christoph Hellwig
2023-09-05 7:44 ` Christoph Hellwig
2023-09-05 9:26 ` Aleksandr Nogikh
2023-09-05 10:04 ` syzbot [this message]
2023-09-05 12:26 ` [syzbot] [block] " Christoph Hellwig
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=000000000000d9daf4060499c0c9@google.com \
--to=syzbot+4a08ffdf3667b36650a1@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nogikh@google.com \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=yukuai3@huawei.com \
--cc=zhang_shurong@foxmail.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).