From: syzbot <syzbot+e0055ea09f1f5e6fabdd@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, pvmohammedanees2003@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_get_system_file_inode
Date: Thu, 19 Sep 2024 13:35:01 -0700 [thread overview]
Message-ID: <66ec8af5.050a0220.29194.0046.GAE@google.com> (raw)
In-Reply-To: <CAABpPxQ-H8MjYrG3VUdR-rUFDrnVwJ5aFJaXFGJ2GpJYWD65pQ@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+e0055ea09f1f5e6fabdd@syzkaller.appspotmail.com
Tested-by: syzbot+e0055ea09f1f5e6fabdd@syzkaller.appspotmail.com
Tested on:
commit: 2004cef1 Merge tag 'sched-core-2024-09-19' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16cd6607980000
kernel config: https://syzkaller.appspot.com/x/.config?x=38d475ce6711b8b4
dashboard link: https://syzkaller.appspot.com/bug?extid=e0055ea09f1f5e6fabdd
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=17a13b00580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-09-19 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAABpPxQ-H8MjYrG3VUdR-rUFDrnVwJ5aFJaXFGJ2GpJYWD65pQ@mail.gmail.com>
2024-09-19 20:35 ` syzbot [this message]
[not found] <CAABpPxTRUTjc_S-i_Z+o9fDzi4JtGiKN2VeaXQngeioqh3d+zA@mail.gmail.com>
2024-09-24 9:25 ` [syzbot] [ocfs2?] possible deadlock in ocfs2_get_system_file_inode syzbot
[not found] <CAABpPxQg+RmC_7udiOmj49MuP3E1B+6bbQQiyTrzzEz0Qei1QA@mail.gmail.com>
2024-09-23 12:18 ` syzbot
2024-08-15 10:46 syzbot
2024-09-14 7:53 ` 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=66ec8af5.050a0220.29194.0046.GAE@google.com \
--to=syzbot+e0055ea09f1f5e6fabdd@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pvmohammedanees2003@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 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.