Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Lutomirski <luto@kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>
Cc: Dave Hansen <dave.hansen@intel.com>,
	stable@vger.kernel.org,
	syzbot+2067e764dbcd10721e2e@syzkaller.appspotmail.com
Subject: Re: [RFC v2 1/2] x86/fpu: Fix state corruption in __fpu__restore_sig()
Date: Wed, 02 Jun 2021 01:17:01 +0200	[thread overview]
Message-ID: <87pmx518gi.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <878s3u34iy.ffs@nanos.tec.linutronix.de>

On Tue, Jun 01 2021 at 00:46, Thomas Gleixner wrote:
> I'm too tired now to test the xstateregs_set() muck, but if you want to
> have a look:
>
>      https://tglx.de/~tglx/patches.tar

And of course the last patch in that series was f*cked up by me. Working
set with all updates included is available at the URL above.

Thanks,

        tglx

  parent reply	other threads:[~2021-06-01 23:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1622351443.git.luto@kernel.org>
2021-05-30  5:12 ` [RFC v2 1/2] x86/fpu: Fix state corruption in __fpu__restore_sig() Andy Lutomirski
2021-05-30 22:02   ` Thomas Gleixner
2021-05-30 23:41     ` Andy Lutomirski
2021-05-31  9:03       ` Thomas Gleixner
2021-05-31 10:01   ` Thomas Gleixner
2021-05-31 18:56     ` Thomas Gleixner
2021-05-31 19:30       ` Andy Lutomirski
2021-05-31 22:46         ` Thomas Gleixner
2021-06-01  4:58           ` Andy Lutomirski
2021-06-01 14:48             ` Dave Hansen
2021-06-01 18:06             ` [PATCH v3 3/5] x86/fpu: Clean up the fpu__clear() variants Dave Hansen
2021-06-01 18:14               ` Andy Lutomirski
2021-06-01 18:35                 ` Dave Hansen
2021-06-01 22:44                   ` Andy Lutomirski
2021-06-01 18:25               ` Thomas Gleixner
2021-06-01 23:17           ` Thomas Gleixner [this message]
2021-05-31 19:48       ` [RFC v2 1/2] x86/fpu: Fix state corruption in __fpu__restore_sig() Thomas Gleixner

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=87pmx518gi.ffs@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=dave.hansen@intel.com \
    --cc=luto@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+2067e764dbcd10721e2e@syzkaller.appspotmail.com \
    --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