From: syzbot <syzbot+6bf948e47f9bac7aacfa@syzkaller.appspotmail.com>
To: ipravdin.official@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] possible deadlock in __ocfs2_flush_truncate_log
Date: Fri, 04 Jul 2025 20:42:02 -0700 [thread overview]
Message-ID: <68689f0a.a00a0220.c7b3.002e.GAE@google.com> (raw)
In-Reply-To: <srmiqb5n6iqsxric6cbkrpinsfcblpowhpijfzjjakiyhs4och@2vrutii673vc>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+6bf948e47f9bac7aacfa@syzkaller.appspotmail.com
Tested-by: syzbot+6bf948e47f9bac7aacfa@syzkaller.appspotmail.com
Tested on:
commit: a79a588f Merge tag 'pm-6.16-rc5' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1492ec8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=418cb04d9a81846c
dashboard link: https://syzkaller.appspot.com/bug?extid=6bf948e47f9bac7aacfa
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=11bac582580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-07-05 3:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <srmiqb5n6iqsxric6cbkrpinsfcblpowhpijfzjjakiyhs4och@2vrutii673vc>
2025-07-05 3:42 ` syzbot [this message]
[not found] <kl7jac3bqyd3dz4uj5rp3dwam6rdbegvf5qahgn7njdaeodndj@aq7yil27yawv>
2025-07-05 3:06 ` [syzbot] [ocfs2?] possible deadlock in __ocfs2_flush_truncate_log syzbot
2025-07-05 3:10 ` Ivan Pravdin
2025-07-05 3:12 ` syzbot
2025-03-15 11:28 syzbot
2025-07-05 3:03 ` syzbot
2025-07-05 3:16 ` 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=68689f0a.a00a0220.c7b3.002e.GAE@google.com \
--to=syzbot+6bf948e47f9bac7aacfa@syzkaller.appspotmail.com \
--cc=ipravdin.official@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