From: syzbot <syzbot+f60c5689d74d066ddd1a@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [hfs?] WARNING in check_flush_dependency (2)
Date: Sat, 15 Apr 2023 02:31:42 -0700 [thread overview]
Message-ID: <0000000000002882fb05f95ca0c2@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 0d3eb744aed4 Merge tag 'urgent-rcu.2023.04.07a' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=132ae59bc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c21559e740385326
dashboard link: https://syzkaller.appspot.com/bug?extid=f60c5689d74d066ddd1a
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, 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/a02928003efa/disk-0d3eb744.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7839447005a4/vmlinux-0d3eb744.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d26ab3184148/bzImage-0d3eb744.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f60c5689d74d066ddd1a@syzkaller.appspotmail.com
------------[ cut here ]------------
workqueue: WQ_MEM_RECLAIM dio/loop3:dio_aio_complete_work is flushing !WQ_MEM_RECLAIM events_long:flush_mdb
WARNING: CPU: 1 PID: 5167 at kernel/workqueue.c:2729 check_flush_dependency+0x29b/0x3f0 kernel/workqueue.c:2729
Modules linked in:
CPU: 1 PID: 5167 Comm: kworker/1:4 Not tainted 6.3.0-rc6-syzkaller-00016-g0d3eb744aed4 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
Workqueue: dio/loop3 dio_aio_complete_work
RIP: 0010:check_flush_dependency+0x29b/0x3f0 kernel/workqueue.c:2729
Code: 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 3f 01 00 00 48 8b 53 18 49 8d b6 60 01 00 00 4d 89 e0 48 c7 c7 c0 67 4b 8a e8 75 e3 f8 ff <0f> 0b e9 e8 fd ff ff e8 19 5e 30 00 65 4c 8b 2c 25 80 b8 03 00 4c
RSP: 0018:ffffc9000478fa60 EFLAGS: 00010086
RAX: 0000000000000000 RBX: ffff88802a40f500 RCX: 0000000000000000
RDX: ffff8880213357c0 RSI: ffffffff814b6237 RDI: 0000000000000001
RBP: ffff888012471400 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff82502670
R13: 0000000000000000 R14: ffff88802b3cf400 R15: ffffc9000478fb00
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020710000 CR3: 000000003c040000 CR4: 0000000000350ee0
Call Trace:
<TASK>
start_flush_work kernel/workqueue.c:3133 [inline]
__flush_work+0x281/0xb60 kernel/workqueue.c:3173
hfs_file_fsync+0x108/0x1a0 fs/hfs/inode.c:683
vfs_fsync_range+0x13e/0x230 fs/sync.c:188
generic_write_sync include/linux/fs.h:2452 [inline]
dio_complete+0x796/0xa80 fs/direct-io.c:309
process_one_work+0x991/0x15c0 kernel/workqueue.c:2390
worker_thread+0x669/0x1090 kernel/workqueue.c:2537
kthread+0x2e8/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</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.
reply other threads:[~2023-04-15 9:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0000000000002882fb05f95ca0c2@google.com \
--to=syzbot+f60c5689d74d066ddd1a@syzkaller.appspotmail.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).