public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+52fb13daf83df5a1b81a@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] INFO: The task syz-executor:NUM has been waiting for writeback completion for more than NUM seconds.
Date: Mon, 30 Mar 2026 10:02:25 -0700	[thread overview]
Message-ID: <69caaca1.a70a0220.97f31.01de.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    7aaa8047eafd Linux 7.0-rc6
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16271a48580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6754c86e8d9e4c91
dashboard link: https://syzkaller.appspot.com/bug?extid=52fb13daf83df5a1b81a
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ba4c84dc7f81/disk-7aaa8047.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/24a0b91bd406/vmlinux-7aaa8047.xz
kernel image: https://storage.googleapis.com/syzbot-assets/71276b7ae1be/bzImage-7aaa8047.xz

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

INFO: The task syz-executor:19624 has been waiting for writeback completion for more than 142 seconds.
INFO: The task syz-executor:19624 has been waiting for writeback completion for more than 142 seconds.


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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

                 reply	other threads:[~2026-03-30 17:02 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=69caaca1.a70a0220.97f31.01de.GAE@google.com \
    --to=syzbot+52fb13daf83df5a1b81a@syzkaller.appspotmail.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