From: syzbot <syzbot+61ce80689253f42e6d80@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, mhiramat@kernel.org,
mingo@redhat.com, oleg@redhat.com, olsajiri@gmail.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tglx@kernel.org, x86@kernel.org
Subject: Re: [syzbot] [trace?] general protection fault in mtree_load
Date: Wed, 01 Jul 2026 02:42:00 -0700 [thread overview]
Message-ID: <6a44e0e8.61501845.2b2b6.0001.GAE@google.com> (raw)
In-Reply-To: <akTZNgy1UPQdNcO_@redhat.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+61ce80689253f42e6d80@syzkaller.appspotmail.com
Tested-by: syzbot+61ce80689253f42e6d80@syzkaller.appspotmail.com
Tested on:
commit: 665159e2 Merge tag 'probes-fixes-v7.2-rc1' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14f7b11c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f9bf5d2bfae96234
dashboard link: https://syzkaller.appspot.com/bug?extid=61ce80689253f42e6d80
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=1084b9fa580000
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2026-07-01 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 6:59 [syzbot] [trace?] general protection fault in mtree_load syzbot
2026-06-22 13:04 ` Oleg Nesterov
2026-06-24 7:49 ` Jiri Olsa
2026-07-01 1:32 ` syzbot
2026-07-01 9:09 ` Oleg Nesterov
2026-07-01 9:42 ` syzbot [this message]
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=6a44e0e8.61501845.2b2b6.0001.GAE@google.com \
--to=syzbot+61ce80689253f42e6d80@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=olsajiri@gmail.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
/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