Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Barret Rhoden <brho@google.com>
Subject: AVX register corruption from signal delivery
To:     Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
        "Rik van Riel\"" <riel@surriel.com>
Cc:     x86@kernel.org, linux-kernel@vger.kernel.org,
        Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>
Message-ID: <c87e93c3-5f30-f242-74b7-6c7ccc91158a@google.com>
Date:   Tue, 26 Nov 2019 14:49:55 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.9.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi -

The Go Team found a bug[1] where the AVX registers can get corrupted 
during signal delivery.  They were able to bisect it to commits related 
to the "x86: load FPU registers on return to userland" patchset[2].

The bug requires the kernel to be built with GCC 9 to trigger.  In 
particular, arch/x86/kernel/fpu/signal.c needs to be built with GCC 9.

Thanks,

Barret

[1] https://bugzilla.kernel.org/show_bug.cgi?id=205663
[2] 
https://lore.kernel.org/kvm/20190403164156.19645-1-bigeasy@linutronix.de/