From: syzbot <syzbot+5a64828fcc4c2ad9b04f@syzkaller.appspotmail.com>
To: eadavis@qq.com, jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
linux-kernel@vger.kernel.org, mark@fasheh.com,
ocfs2-devel@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] general protection fault in ocfs2_prepare_dir_for_insert
Date: Tue, 20 Aug 2024 04:42:04 -0700 [thread overview]
Message-ID: <0000000000002732eb06201beaf7@google.com> (raw)
In-Reply-To: <tencent_152025FEBA06BB5533C69ED71B124BA11B08@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+5a64828fcc4c2ad9b04f@syzkaller.appspotmail.com
Tested-by: syzbot+5a64828fcc4c2ad9b04f@syzkaller.appspotmail.com
Tested on:
commit: b0da6408 Merge tag 'printk-for-6.11-rc5' of git://git...
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=15c8a7c5980000
kernel config: https://syzkaller.appspot.com/x/.config?x=df2f0ed7e30a639d
dashboard link: https://syzkaller.appspot.com/bug?extid=5a64828fcc4c2ad9b04f
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=15e4dbd3980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-08-20 11:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 7:58 [syzbot] [ocfs2?] general protection fault in ocfs2_prepare_dir_for_insert syzbot
2024-08-20 11:19 ` Edward Adam Davis
2024-08-20 11:42 ` syzbot [this message]
2024-08-20 12:08 ` [PATCH] ocfs2: Add i_size check for dir Edward Adam Davis
2024-08-20 12:44 ` Joseph Qi
2024-08-20 13:55 ` Edward Adam Davis
2024-08-21 10:41 ` Joseph Qi
2024-08-21 11:15 ` Edward Adam Davis
2024-08-20 14:59 ` Matthew Wilcox
2024-08-21 6:16 ` heming.zhao
2024-08-21 9:08 ` Edward Adam Davis
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=0000000000002732eb06201beaf7@google.com \
--to=syzbot+5a64828fcc4c2ad9b04f@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--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