From: syzbot <syzbot+386ce9e60fa1b18aac5b@syzkaller.appspotmail.com>
To: andrew.kanner@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] general protection fault in ocfs2_xa_block_wipe_namevalue
Date: Sun, 03 Nov 2024 11:25:02 -0800 [thread overview]
Message-ID: <6727ce0e.050a0220.3c8d68.0a8b.GAE@google.com> (raw)
In-Reply-To: <6727c3ac.170a0220.27f534.dc51@mx.google.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+386ce9e60fa1b18aac5b@syzkaller.appspotmail.com
Tested-by: syzbot+386ce9e60fa1b18aac5b@syzkaller.appspotmail.com
Tested on:
commit: 886b7e80 Merge tag 'driver-core-6.12-rc6' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=120b4587980000
kernel config: https://syzkaller.appspot.com/x/.config?x=35698c25466f388c
dashboard link: https://syzkaller.appspot.com/bug?extid=386ce9e60fa1b18aac5b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=133efaa7980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-11-03 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6727c3ac.170a0220.27f534.dc51@mx.google.com>
2024-11-03 19:25 ` syzbot [this message]
2024-11-02 16:37 [syzbot] [ocfs2?] general protection fault in [v2] ocfs2_xa_block_wipe_namevalue Andrew Kanner
2024-11-03 19:05 ` [syzbot] [ocfs2?] general protection fault in ocfs2_xa_block_wipe_namevalue syzbot
[not found] <67215651.a70a0220.31b018.c8d7@mx.google.com>
2024-10-29 22:00 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2024-10-27 10:19 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=6727ce0e.050a0220.3c8d68.0a8b.GAE@google.com \
--to=syzbot+386ce9e60fa1b18aac5b@syzkaller.appspotmail.com \
--cc=andrew.kanner@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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