From: syzbot <syzbot+4d24267b490e2b68a5fa@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, pz010001011111@proton.me,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] possible deadlock in bch2_replicas_entry_validate
Date: Mon, 07 Oct 2024 13:31:02 -0700 [thread overview]
Message-ID: <67044506.050a0220.49194.0519.GAE@google.com> (raw)
In-Reply-To: <kQXi06MMqFpJHpnTUVuy1lTREJ1DVh1obmiDutmzESdyf1fd2z6pgLfGa32VsBMugcR38-G11y_XLb7M2f6IDWu6OJhnKsp-taulKl3c2sU=@proton.me>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+4d24267b490e2b68a5fa@syzkaller.appspotmail.com
Tested-by: syzbot+4d24267b490e2b68a5fa@syzkaller.appspotmail.com
Tested on:
commit: 87d6aab2 Merge tag 'for_linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=173ca707980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7a3fccdd0bb995
dashboard link: https://syzkaller.appspot.com/bug?extid=4d24267b490e2b68a5fa
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=170ca707980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-10-07 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <kQXi06MMqFpJHpnTUVuy1lTREJ1DVh1obmiDutmzESdyf1fd2z6pgLfGa32VsBMugcR38-G11y_XLb7M2f6IDWu6OJhnKsp-taulKl3c2sU=@proton.me>
2024-10-07 20:31 ` syzbot [this message]
[not found] <0uXIx6_m3Tho5irFNPyOCVxkEwglXY68vmpOxPp7JMeSZQl-lCrilzFNqzy_Z7yscH3dc1oeZ3zY0rwJF4IBvqa_uNjFDRermHIphBt2YgE=@proton.me>
2024-10-07 22:09 ` [syzbot] [bcachefs?] possible deadlock in bch2_replicas_entry_validate syzbot
2024-10-03 17:42 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=67044506.050a0220.49194.0519.GAE@google.com \
--to=syzbot+4d24267b490e2b68a5fa@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pz010001011111@proton.me \
--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