All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+1d096d31de6a0491b55e@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, rafad900@gmail.com,
	 skhan@linuxfoundation.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [jfs] general protection fault in txEnd
Date: Mon, 30 Mar 2026 14:45:01 -0700	[thread overview]
Message-ID: <69caeedd.a70a0220.97f31.020a.GAE@google.com> (raw)
In-Reply-To: <acrn5bxN51_yj93Q@tradnomic.core>

Hello,

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

failed to apply patch:
checking file fs/jfs/namei.c
Hunk #1 FAILED at 99.
1 out of 1 hunk FAILED



Tested on:

commit:         d0c3bcd5 Merge tag 'libcrypto-for-linus' of git://git...
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=14b6a9313e132a6b
dashboard link: https://syzkaller.appspot.com/bug?extid=1d096d31de6a0491b55e
compiler:       
patch:          https://syzkaller.appspot.com/x/patch.diff?x=168d01ca580000


  reply	other threads:[~2026-03-30 21:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 21:15 [syzbot] [jfs?] [fat?] general protection fault in txEnd Rafael Alejandro Diaz Cruz
2026-03-30 21:45 ` syzbot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-30 23:32 Rafael Alejandro Diaz Cruz
2026-03-31  0:19 ` [syzbot] [jfs] " syzbot
2026-03-28  2:20 [syzbot] [jfs?] [fat?] " Rafael Alejandro Diaz Cruz
2026-03-29 11:07 ` [syzbot] [jfs] " syzbot
     [not found] <CALp66yFze81g4MhLZfqxyqLpH0RRsHfyXcXPjWUY-G-EFWiB2g@mail.gmail.com>
2026-03-28  1:33 ` syzbot
     [not found]   ` <CALp66yEShffuRpH4CxvanWanShtavxGtZfO0Sj8+QCaj6mO1FQ@mail.gmail.com>
2026-03-28  1:46     ` syzbot
2026-03-28  1:49     ` Rafael Alejandro Díaz Cruz
2026-03-28  1:51       ` 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=69caeedd.a70a0220.97f31.020a.GAE@google.com \
    --to=syzbot+1d096d31de6a0491b55e@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafad900@gmail.com \
    --cc=skhan@linuxfoundation.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.