public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+9489c9f9f3d437221ea2@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	 yun.zhou@windriver.com
Subject: Re: [syzbot] [jfs?] general protection fault in txCommit (2)
Date: Sat, 08 Nov 2025 00:36:02 -0800	[thread overview]
Message-ID: <690f00f2.a70a0220.22f260.007a.GAE@google.com> (raw)
In-Reply-To: <e7ea1bff-0b4e-4490-b5a7-e8e366944842@windriver.com>

Hello,

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

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



Tested on:

commit:         e811c33b Merge tag 'drm-fixes-2025-11-08' of https://g..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=41ad820f608cb833
dashboard link: https://syzkaller.appspot.com/bug?extid=9489c9f9f3d437221ea2
compiler:       
patch:          https://syzkaller.appspot.com/x/patch.diff?x=177f4412580000


       reply	other threads:[~2025-11-08  8:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e7ea1bff-0b4e-4490-b5a7-e8e366944842@windriver.com>
2025-11-08  8:36 ` syzbot [this message]
     [not found] <SJ5PPF2F7FC4EE60B34FA683FC9B5F3EAFE9FCAA@SJ5PPF2F7FC4EE6.namprd11.prod.outlook.com>
2025-11-14 15:15 ` [syzbot] [jfs?] general protection fault in txCommit (2) syzbot
     [not found] <SJ5PPF2F7FC4EE6AC25CE1A7769CDC692799FCAA@SJ5PPF2F7FC4EE6.namprd11.prod.outlook.com>
2025-11-14 14:51 ` syzbot
     [not found] <912d60c8-e898-4113-b167-9549bc15f026@windriver.com>
2025-11-10 13:07 ` syzbot
     [not found] <bf35b502-ca85-41a4-b47b-c3ae63155257@windriver.com>
2025-11-10 12:12 ` syzbot
     [not found] <SJ5PPF2F7FC4EE603CDF9A16121B88A38C09FC0A@SJ5PPF2F7FC4EE6.namprd11.prod.outlook.com>
2025-11-08 16:46 ` syzbot
2025-11-07  7:29 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=690f00f2.a70a0220.22f260.007a.GAE@google.com \
    --to=syzbot+9489c9f9f3d437221ea2@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yun.zhou@windriver.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