public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+c7604c9fdd7580cca4e0@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] INFO: task jbd2/sda1-NUM:NUM blocked in I/O wait for more than NUM seconds.
Date: Fri, 01 May 2026 17:47:01 -0700	[thread overview]
Message-ID: <69f54985.050a0220.312cd3.001f.GAE@google.com> (raw)
In-Reply-To: <20260502000247.123877-1-kartikey406@gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+c7604c9fdd7580cca4e0@syzkaller.appspotmail.com
Tested-by: syzbot+c7604c9fdd7580cca4e0@syzkaller.appspotmail.com

Tested on:

commit:         cd546f7a Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=143a2ece580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d0f0911eedbc130a
dashboard link: https://syzkaller.appspot.com/bug?extid=c7604c9fdd7580cca4e0
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch:          https://syzkaller.appspot.com/x/patch.diff?x=11c50a36580000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2026-05-02  0:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260502000247.123877-1-kartikey406@gmail.com>
2026-05-02  0:47 ` syzbot [this message]
     [not found] <20260504012222.13898-1-kartikey406@gmail.com>
2026-05-04  1:51 ` [syzbot] [ext4?] INFO: task jbd2/sda1-NUM:NUM blocked in I/O wait for more than NUM seconds syzbot
     [not found] <20260501234725.122250-1-kartikey406@gmail.com>
2026-05-02  0:18 ` syzbot
2026-05-01  0:18 [syzbot] " syzbot
2026-05-01 14:48 ` [syzbot] [ext4?] " syzbot

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=69f54985.050a0220.312cd3.001f.GAE@google.com \
    --to=syzbot+c7604c9fdd7580cca4e0@syzkaller.appspotmail.com \
    --cc=kartikey406@gmail.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