From: syzbot <syzbot+8346a1aeed52cb04c9ba@syzkaller.appspotmail.com>
To: alexandr.lobakin@intel.com, dvyukov@google.com,
jirislaby@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, miklos@szeredi.hu,
mingo@kernel.org, nogikh@google.com,
penguin-kernel@I-love.SAKURA.ne.jp,
penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] unexpected kernel reboot (8)
Date: Fri, 10 Mar 2023 12:53:34 -0800 [thread overview]
Message-ID: <0000000000006b11b005f691f4b9@google.com> (raw)
In-Reply-To: <0000000000008af58705e9b32b1d@google.com>
syzbot suspects this issue was fixed by commit:
commit 7734a0f31e99c433df3063bbb7e8ee5a16a2cb82
Author: Alexander Lobakin <alexandr.lobakin@intel.com>
Date: Mon Jan 9 17:04:02 2023 +0000
x86/boot: Robustify calling startup_{32,64}() from the decompressor code
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14606624c80000
start commit: 1fe4fd6f5cad Merge tag 'xfs-6.2-fixes-2' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=edc860b1c9b6751
dashboard link: https://syzkaller.appspot.com/bug?extid=8346a1aeed52cb04c9ba
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12baac4a480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=118bf42c480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: x86/boot: Robustify calling startup_{32,64}() from the decompressor code
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-03-10 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000008af58705e9b32b1d@google.com>
2022-09-28 7:35 ` [syzbot] unexpected kernel reboot (8) Dmitry Vyukov
2023-03-10 20:53 ` 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=0000000000006b11b005f691f4b9@google.com \
--to=syzbot+8346a1aeed52cb04c9ba@syzkaller.appspotmail.com \
--cc=alexandr.lobakin@intel.com \
--cc=dvyukov@google.com \
--cc=jirislaby@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mingo@kernel.org \
--cc=nogikh@google.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--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;
as well as URLs for NNTP newsgroup(s).