public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Mon, 04 May 2026 14:23:02 -0700	[thread overview]
Message-ID: <69f90e36.170a0220.bb392.0009.GAE@google.com> (raw)
In-Reply-To: <20260429015807.102606-1-kartikey406@gmail.com>

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

failed to apply patch:
checking file fs/hfsplus/super.c
Hunk #1 succeeded at 375 (offset 3 lines).
Hunk #2 succeeded at 448 (offset 3 lines).
Hunk #3 FAILED at 645.
Hunk #4 succeeded at 711 (offset 27 lines).
1 out of 4 hunks FAILED



Tested on:

commit:         c7e4e4d5 Merge tag 'for-linus-7.1-2' of https://github..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=bcb138057684c76a
dashboard link: https://syzkaller.appspot.com/bug?extid=c0ba772a362e70937dfb
compiler:       
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1185b896580000


       reply	other threads:[~2026-05-04 21:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260429015807.102606-1-kartikey406@gmail.com>
2026-05-04 21:23 ` 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] <20260414233617.75833-1-kartikey406@gmail.com>
2026-04-15  1:37 ` 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=69f90e36.170a0220.bb392.0009.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox