From: syzbot <syzbot+c0ba772a362e70937dfb@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] general protection fault in hfsplus_cat_write_inode
Date: Tue, 14 Apr 2026 18:37:02 -0700 [thread overview]
Message-ID: <69deebbe.a00a0220.468cb.006d.GAE@google.com> (raw)
In-Reply-To: <20260414233617.75833-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+c0ba772a362e70937dfb@syzkaller.appspotmail.com
Tested-by: syzbot+c0ba772a362e70937dfb@syzkaller.appspotmail.com
Tested on:
commit: e997ac58 Merge tag 'linux_kselftest-next-7.1-rc1' of g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10f6fcd2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8121d5de65640618
dashboard link: https://syzkaller.appspot.com/bug?extid=c0ba772a362e70937dfb
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=14f184ce580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-04-15 1:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260414233617.75833-1-kartikey406@gmail.com>
2026-04-15 1:37 ` syzbot [this message]
[not found] <20260428092309.95636-1-kartikey406@gmail.com>
2026-05-04 21:23 ` [syzbot] [hfs?] general protection fault in hfsplus_cat_write_inode syzbot
[not found] <20260429015807.102606-1-kartikey406@gmail.com>
2026-05-04 21:23 ` syzbot
[not found] <20260413230242.56985-1-kartikey406@gmail.com>
2026-04-14 1:00 ` syzbot
2026-04-13 21:50 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=69deebbe.a00a0220.468cb.006d.GAE@google.com \
--to=syzbot+c0ba772a362e70937dfb@syzkaller.appspotmail.com \
--cc=kartikey406@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 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.