From: syzbot <syzbot+9013411dc43f3582823a@syzkaller.appspotmail.com>
To: kmehltretter@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] INFO: task hung in gfs2_recover_journal (4)
Date: Wed, 22 Jul 2026 20:57:03 -0700 [thread overview]
Message-ID: <6a61910f.16bfb6d0.3c48cb.000a.GAE@google.com> (raw)
In-Reply-To: <20260723025728.43981-1-kmehltretter@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
lost connection to test machine
Tested on:
commit: 4539944e Merge tag 'liveupdate-fixes-2026-07-22' of gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15e70ab9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ddc41d77cdc6965a
dashboard link: https://syzkaller.appspot.com/bug?extid=9013411dc43f3582823a
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=10b8aab9580000
next parent reply other threads:[~2026-07-23 3:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260723025728.43981-1-kmehltretter@gmail.com>
2026-07-23 3:57 ` syzbot [this message]
[not found] <20260723043654.48231-1-kmehltretter@gmail.com>
2026-07-23 5:40 ` [syzbot] [gfs2?] INFO: task hung in gfs2_recover_journal (4) syzbot
[not found] <20260324092747.1459265-1-kartikey406@gmail.com>
2026-03-24 9:46 ` syzbot
[not found] <20260324023042.1453608-1-kartikey406@gmail.com>
2026-03-24 2:48 ` syzbot
[not found] <20260324014901.1451209-1-kartikey406@gmail.com>
2026-03-24 2:21 ` syzbot
2026-03-23 20:13 syzbot
2026-03-25 7:37 ` Edward Adam Davis
2026-03-25 8:18 ` syzbot
2026-03-25 7:49 ` Edward Adam Davis
2026-03-25 8:30 ` syzbot
2026-03-25 10:25 ` Edward Adam Davis
2026-03-25 11:24 ` 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=6a61910f.16bfb6d0.3c48cb.000a.GAE@google.com \
--to=syzbot+9013411dc43f3582823a@syzkaller.appspotmail.com \
--cc=kmehltretter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.