From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Lutomirski <luto@kernel.org>,
syzbot <syzbot+2067e764dbcd10721e2e@syzkaller.appspotmail.com>,
bp@alien8.de, bp@suse.de, dave.hansen@linux.intel.com,
fenghua.yu@intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tony.luck@intel.com, x86@kernel.org, yu-cheng.yu@intel.com
Subject: Re: [syzbot] WARNING in ex_handler_fprestore
Date: Thu, 27 May 2021 00:03:03 +0200 [thread overview]
Message-ID: <87sg29886g.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <fe20f360-7c6c-f1bf-c3a5-403ae979fae6@kernel.org>
On Tue, May 25 2021 at 17:33, Andy Lutomirski wrote:
> On 5/24/21 1:51 AM, syzbot wrote:
> I entirely believe that this bug is real and that syzbot bisected it
> correctly, but I'm puzzled by the reproducer. It says:
The bug is real and the bisection is correct.
> ptrace$setregs(0xd, r0, 0x0, &(0x7f0000000080))
>
> I would really, really expect this to result from PTRACE_SETREGSET or
> PTRACE_SETFPREGS, but this is PTRACE_SETREGS.
>
> Am I missing something really obvious here?
That ptrace muck is a red herring and has nothing to do with it.
I decoded it fully by now and will send out coherent info (and hopefully
a patch) tomorrow with brain awake. Time for bed here...
Thanks,
tglx
next prev parent reply other threads:[~2021-05-26 22:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 8:51 [syzbot] WARNING in ex_handler_fprestore syzbot
2021-05-26 0:33 ` Andy Lutomirski
2021-05-26 7:00 ` Dmitry Vyukov
2021-05-26 21:21 ` Yu, Yu-cheng
2021-05-26 22:37 ` Andy Lutomirski
2021-05-26 22:03 ` Thomas Gleixner [this message]
2021-05-27 16:49 ` Thomas Gleixner
2021-05-27 18:59 ` Yu, Yu-cheng
2021-05-27 19:17 ` Thomas Gleixner
2021-05-27 19:05 ` Thomas Gleixner
2021-05-31 17:46 ` 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=87sg29886g.ffs@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzbot+2067e764dbcd10721e2e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.