From: syzbot <syzbot+b4a2af3000eaa84d95d5@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] general protection fault in create_empty_buffers (5)
Date: Fri, 09 Jan 2026 01:31:01 -0800 [thread overview]
Message-ID: <6960cad5.050a0220.1c677c.03c1.GAE@google.com> (raw)
In-Reply-To: <20260109090943.585561-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+b4a2af3000eaa84d95d5@syzkaller.appspotmail.com
Tested-by: syzbot+b4a2af3000eaa84d95d5@syzkaller.appspotmail.com
Tested on:
commit: 623fb991 Merge tag 'pinctrl-v6.19-2' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10e6b1fc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a11e0f726bfb6765
dashboard link: https://syzkaller.appspot.com/bug?extid=b4a2af3000eaa84d95d5
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1513583a580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-01-09 9:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260109090943.585561-1-kartikey406@gmail.com>
2026-01-09 9:31 ` syzbot [this message]
[not found] <20260109084313.584239-1-kartikey406@gmail.com>
2026-01-09 9:00 ` syzbot
[not found] <20260109080649.582553-1-kartikey406@gmail.com>
2026-01-09 8:25 ` syzbot
[not found] <20260109054404.349244-1-kartikey406@gmail.com>
2026-01-09 6:43 ` syzbot
2026-01-08 13:00 syzbot
2026-01-09 4:30 ` Edward Adam Davis
2026-01-09 4:50 ` syzbot
2026-01-09 10:49 ` Edward Adam Davis
2026-01-09 11:04 ` syzbot
2026-01-09 11:14 ` Edward Adam Davis
2026-01-09 11:36 ` 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=6960cad5.050a0220.1c677c.03c1.GAE@google.com \
--to=syzbot+b4a2af3000eaa84d95d5@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
Powered by JetHome