From: syzbot <syzbot+1fed2de07d8e11a3ec1b@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_try_remove_refcount_tree
Date: Sat, 21 Jun 2025 08:05:04 -0700 [thread overview]
Message-ID: <6856ca20.a00a0220.137b3.007a.GAE@google.com> (raw)
In-Reply-To: <9a1a4a25-f7cb-4eaa-bcaa-d655a444076f@I-love.SAKURA.ne.jp>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+1fed2de07d8e11a3ec1b@syzkaller.appspotmail.com
Tested-by: syzbot+1fed2de07d8e11a3ec1b@syzkaller.appspotmail.com
Tested on:
commit: 3f75bfff Merge tag 'mtd/fixes-for-6.16-rc3' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1730f30c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a237c32900fc479
dashboard link: https://syzkaller.appspot.com/bug?extid=1fed2de07d8e11a3ec1b
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
patch: https://syzkaller.appspot.com/x/patch.diff?x=158ac182580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-06-21 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 8:48 [syzbot] [ocfs2?] possible deadlock in ocfs2_try_remove_refcount_tree syzbot
2024-08-21 9:32 ` Edward Adam Davis
2024-08-21 9:48 ` syzbot
2024-08-21 21:04 ` [syzbot] " syzbot
2025-06-21 16:03 ` Tetsuo Handa
2025-07-14 21:57 ` Tetsuo Handa
2024-09-23 22:04 ` [syzbot] [ocfs2?] " syzbot
2025-06-21 14:27 ` Tetsuo Handa
2025-06-21 15:05 ` syzbot [this message]
2025-07-19 17:11 ` Forwarded: " syzbot
[not found] <20240821210432.146003-1-djahchankoike@gmail.com>
2024-08-21 21:20 ` syzbot
[not found] <690ae6be-8313-46eb-a546-b895f5a7227c@I-love.SAKURA.ne.jp>
2025-07-19 18:22 ` 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=6856ca20.a00a0220.137b3.007a.GAE@google.com \
--to=syzbot+1fed2de07d8e11a3ec1b@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--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.