From: syzbot <syzbot+797d4829dafe3f11dce7@syzkaller.appspotmail.com>
To: eadavis@qq.com, heming.zhao@suse.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?] kernel BUG in ocfs2_read_virt_blocks
Date: Mon, 14 Oct 2024 00:00:02 -0700 [thread overview]
Message-ID: <670cc172.050a0220.3e960.0058.GAE@google.com> (raw)
In-Reply-To: <658bf0ce-9565-4b47-9043-a853374a74fa@suse.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+797d4829dafe3f11dce7@syzkaller.appspotmail.com
Tested-by: syzbot+797d4829dafe3f11dce7@syzkaller.appspotmail.com
Tested on:
commit: 6485cf5e Merge tag 'hid-for-linus-2024101301' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17169440580000
kernel config: https://syzkaller.appspot.com/x/.config?x=164d2822debd8b0d
dashboard link: https://syzkaller.appspot.com/bug?extid=797d4829dafe3f11dce7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=12e20030580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-10-14 7:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 9:51 [syzbot] [ocfs2?] kernel BUG in ocfs2_read_virt_blocks syzbot
2024-10-13 6:19 ` Edward Adam Davis
2024-10-13 7:29 ` [syzbot] " syzbot
2024-10-13 13:25 ` [PATCH] ocfs2: BUG is meaningless when the flags is 0 Edward Adam Davis
2024-10-13 23:31 ` [PATCH V2] " Edward Adam Davis
2024-10-14 6:28 ` heming.zhao
2024-10-14 7:00 ` syzbot [this message]
2024-10-14 6:33 ` Joseph Qi
2024-10-14 11:47 ` [PATCH V3] ocfs2: add a sanity check for i_size Edward Adam Davis
2024-10-14 12:24 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_read_virt_blocks syzbot
2024-10-16 2:06 ` [PATCH V3] ocfs2: add a sanity check for i_size Joseph Qi
2024-10-16 2:10 ` Joseph Qi
2024-10-16 3:52 ` Edward Adam Davis
2024-10-16 11:08 ` Joseph Qi
2024-10-16 11:57 ` Edward Adam Davis
2024-10-16 12:13 ` Joseph Qi
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=670cc172.050a0220.3e960.0058.GAE@google.com \
--to=syzbot+797d4829dafe3f11dce7@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=heming.zhao@suse.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 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.