From: Dave Hansen <dave.hansen@intel.com>
To: Ivan Zahariev <famzah@icdsoft.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Yu, Yu-cheng" <yu-cheng.yu@intel.com>,
Andy Lutomirski <luto@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: linux-tip-commits@vger.kernel.org,
Fenghua Yu <fenghua.yu@intel.com>, Borislav Petkov <bp@suse.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Tony Luck <tony.luck@intel.com>, x86 <x86@kernel.org>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>
Subject: Re: [tip: x86/fpu] x86/fpu/xstate: Define new functions for clearing fpregs and xstates
Date: Tue, 29 Nov 2022 10:16:58 -0800 [thread overview]
Message-ID: <31b30c00-9de9-2881-53c3-b08804571d6c@intel.com> (raw)
In-Reply-To: <ff5ad474-6d32-8bf8-e297-ed71a967d27c@icdsoft.com>
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?
next prev parent reply other threads:[~2022-11-29 18:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 14:54 [PATCH v4 00/10] Support XSAVES supervisor states Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 01/10] x86/fpu/xstate: Rename validate_xstate_header() to validate_user_xstate_header() Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Fenghua Yu
2020-05-12 14:54 ` [PATCH v4 02/10] x86/fpu/xstate: Define new macros for supervisor and user xstates Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Fenghua Yu
2020-05-12 14:54 ` [PATCH v4 03/10] x86/fpu/xstate: Separate user and supervisor xfeatures mask Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 04/10] x86/fpu/xstate: Introduce XSAVES supervisor states Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 05/10] x86/fpu/xstate: Define new functions for clearing fpregs and xstates Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Fenghua Yu
2021-05-24 16:34 ` Andy Lutomirski
2021-05-25 17:44 ` Yu, Yu-cheng
2021-05-25 18:00 ` Thomas Gleixner
2022-11-29 11:19 ` Ivan Zahariev
2022-11-29 18:16 ` Dave Hansen [this message]
2022-12-01 12:58 ` Ivan Zahariev
2022-12-01 14:04 ` Dave Hansen
2020-05-12 14:54 ` [PATCH v4 06/10] x86/fpu/xstate: Update sanitize_restored_xstate() for supervisor xstates Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 07/10] x86/fpu/xstate: Update copy_kernel_to_xregs_err() for XSAVES supervisor states Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] x86/fpu/xstate: Update copy_kernel_to_xregs_err() for " tip-bot2 for Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 08/10] x86/fpu: Introduce copy_supervisor_to_kernel() Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 09/10] x86/fpu/xstate: Preserve supervisor states for slow path of __fpu__restore_sig() Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] x86/fpu/xstate: Preserve supervisor states for the slow path in __fpu__restore_sig() tip-bot2 for Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 10/10] x86/fpu/xstate: Restore supervisor states for signal return Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Yu-cheng Yu
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=31b30c00-9de9-2881-53c3-b08804571d6c@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=famzah@icdsoft.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@kernel.org \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--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.