[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87sg29886g.ffs@nanos.tec.linutronix.de>
Date: Thu, 27 May 2021 00:03:03 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Andy Lutomirski <luto@...nel.org>,
syzbot <syzbot+2067e764dbcd10721e2e@...kaller.appspotmail.com>,
bp@...en8.de, bp@...e.de, dave.hansen@...ux.intel.com,
fenghua.yu@...el.com, hpa@...or.com, linux-kernel@...r.kernel.org,
mingo@...hat.com, peterz@...radead.org,
syzkaller-bugs@...glegroups.com, tony.luck@...el.com,
x86@...nel.org, yu-cheng.yu@...el.com
Subject: Re: [syzbot] WARNING in ex_handler_fprestore
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
Powered by blists - more mailing lists