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 17:19:02 -0700 [thread overview]
Message-ID: <69cb12f6.a70a0220.97f31.021e.GAE@google.com> (raw)
In-Reply-To: <acsIHnU7DPhd42Bz@tradnomic.core>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+1d096d31de6a0491b55e@syzkaller.appspotmail.com
Tested-by: syzbot+1d096d31de6a0491b55e@syzkaller.appspotmail.com
Tested on:
commit: d0c3bcd5 Merge tag 'libcrypto-for-linus' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10d0241f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=df6930c3610cf79
dashboard link: https://syzkaller.appspot.com/bug?extid=1d096d31de6a0491b55e
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=13168ebf980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-03-31 0:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 23:32 [syzbot] [jfs?] [fat?] general protection fault in txEnd Rafael Alejandro Diaz Cruz
2026-03-31 0:19 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-30 21:15 Rafael Alejandro Diaz Cruz
2026-03-30 21:45 ` [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=69cb12f6.a70a0220.97f31.021e.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox