From: syzbot <syzbot+fe63f377148a6371a9db@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, mmpgouride@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] possible deadlock in pcpu_alloc_noprof
Date: Tue, 25 Feb 2025 00:52:03 -0800 [thread overview]
Message-ID: <67bd84b3.050a0220.bbfd1.00a1.GAE@google.com> (raw)
In-Reply-To: <13EF942E-1B2F-4B04-AB8F-5D93DCA7E4AE@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+fe63f377148a6371a9db@syzkaller.appspotmail.com
Tested-by: syzbot+fe63f377148a6371a9db@syzkaller.appspotmail.com
Tested on:
commit: 5404ebaa bcachefs: Fix deadlock
git tree: https://github.com/alanskind/bcachefs
console output: https://syzkaller.appspot.com/x/log.txt?x=1273c6e4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=19886416c83671c4
dashboard link: https://syzkaller.appspot.com/bug?extid=fe63f377148a6371a9db
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-02-25 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13EF942E-1B2F-4B04-AB8F-5D93DCA7E4AE@gmail.com>
2025-02-25 8:52 ` syzbot [this message]
[not found] <1D76F22E-39A3-4174-9ADE-E3FCA97182BA@gmail.com>
2025-02-26 7:56 ` [syzbot] [bcachefs?] possible deadlock in pcpu_alloc_noprof syzbot
2024-09-29 16:17 syzbot
2025-02-12 4:31 ` syzbot
2025-02-12 9:22 ` Alan Huang
2025-02-12 9:49 ` syzbot
2025-02-24 18:52 ` Alan Huang
2025-02-24 19:17 ` syzbot
2025-05-29 9:09 ` 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=67bd84b3.050a0220.bbfd1.00a1.GAE@google.com \
--to=syzbot+fe63f377148a6371a9db@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmpgouride@gmail.com \
--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