[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <31b30c00-9de9-2881-53c3-b08804571d6c@intel.com>
Date: Tue, 29 Nov 2022 10:16:58 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Ivan Zahariev <famzah@...soft.com>,
Thomas Gleixner <tglx@...utronix.de>,
"Yu, Yu-cheng" <yu-cheng.yu@...el.com>,
Andy Lutomirski <luto@...nel.org>,
LKML <linux-kernel@...r.kernel.org>
Cc: linux-tip-commits@...r.kernel.org,
Fenghua Yu <fenghua.yu@...el.com>,
Borislav Petkov <bp@...e.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Tony Luck <tony.luck@...el.com>, x86 <x86@...nel.org>,
"Shankar, Ravi V" <ravi.v.shankar@...el.com>
Subject: Re: [tip: x86/fpu] x86/fpu/xstate: Define new functions for clearing
fpregs and xstates
On 11/29/22 03:19, Ivan Zahariev wrote:
> Can you please take a look into this bug which syzbot tracked to a
> commit of yours (b860eb8dce5906b14e3a7f3c771e0b3d6ef61b94). Even since
> we switched from kernel 4.14 to 5.15 we are experiencing often random
> segmentation faults with the following error in "dmesg":
Which kernel are you running, exactly? There is a fix for the commit
that you identified:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=484cea4f362e
but it should have been in 5.15.
Is there a chance you could test current mainline and see if the issue
is still there?
Powered by blists - more mailing lists